Improve the EDI tool learn page

[praneesha]

Purpose

Improve the EDI tool learn page.

Fixes #

Checklist

• Page addition

  • Add permalink to pages.

• Page removal

  • Remove entry from corresponding left nav YAML file.
  • Add redirect_from on the alternative page.
  • If no alternative page, add redirection on the redirections.js file.

• Page rename

  • Add front-matter redirect_from.
  • Add front-matter redirect_to: (if applicable).

• Page restrcuture

  • Add permalink to pages.
  • Add front-matter redirect_from.
  • Add front-matter redirect_to: (if applicable).

[anupama-pathirage]

Do we need to have command options part in sub heading too as it is there in main heading?

[praneesha]

As we have the code generation and package generation subheadings repeated under many main headings such as Usage, Command options, and Examples, it is clearer to repeat those in the sub headings as follows.

Usage
    - Code generation usage
    - Package generation usage
Command options
    - Code generation command options
    - Package generation command options
 Examples
    - Code generation example
    - Package generation example

[praneesha]

Also, if we remove the repetition of the words, the URLs of the subheadings will be generated as follows as there will be multiple similar ones.

- /learn/edi-tool/#code-generation-1
- /learn/edi-tool/#code-generation-2
- /learn/edi-tool/#code-generation-3

[praneesha]

However, a better structure would be to have 2 main sections for code and package generation as follows similar to [1].

Code generation
- Code generation usage
- Code generation command options
- Code generation example
Package generation
- Package generation usage
- Package generation command options
- Package generation example

[1] https://ballerina.io/learn/graphql-tool/

[anupama-pathirage]

Yes, we definitely need to fix the structure, as suggested in the last comment above.