Update docs generations

[sfc-gh-jvasquezrojas]

Pre-review checklist

• N/A I've confirmed that instructions included in README.md are still correct after my changes in the codebase.
• I've added or updated automated unit tests to verify correctness of my new code.
• N/A I've added or updated integration tests to verify correctness of my new code.
• I've confirmed that my changes are working by executing CLI's commands manually on MacOS.
• I've confirmed that my changes are working by executing CLI's commands manually on Windows.
• N/A I've confirmed that my changes are up-to-date with the target branch.
• N/A I've described my changes in the release notes.
• I've described my changes in the section below.

Changes description

Update docs generation to generate v20 model

Example output:

definition_entities_application.txt
definition_entities_function.txt

[sfc-gh-jsikorski]

Seems ok. Notified @sfc-gh-mheavin about this PR - i think we need his opinion on this.

[sfc-gh-jsikorski]

Could you add more assertions/test cases to check if proper number of files is generated and their content is ok?

[sfc-gh-mheavin]

• Can we specify the type of code-block [ .. code-block:: json or .. code-block:: yaml ]
• Please add a blank line after the ==== lines before sentences (e.g. The following table...)
• Add periods at the end of the description sentences or fragments
• It shows the schema version as 1.
• Can we get more descriptive descriptions? For example, the type description just says Type.
• For enum values, can we include the enums, especially if the list is relatively short and known. For example, the type of entity.