Jlc/add documentation init

[johanseto]

Description

This PR adds automatic documentation of python code.
Also, add some basic documentation of the features.

Testing instructions

make docs

Open in a web browser the index.html generated file.
docs/build/html/index.html

After

• Check the contents section is a little summary of the repo.

Screencast.from.20-05-25.17.42.54.webm

• Check the api_package, is friendly documentation if the dosctring of functions and module works.
  Check validators eg

Screencast.from.20-05-25.17.43.41.webm

Additional information

Include anything else that will help reviewers and consumers understand the change.

• Does this change depend on other changes elsewhere?
• Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.
• Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.

Checklist for Merge

• Tested in a remote environment
• Updated documentation
• Rebased master/main
• Squashed commits

TO-DO:

Improve the documentation fixing docstrings or hints of warning in some modules.

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[andrey-canon]

I checked the description pr and I like the result, however, there is a misunderstanding since the idea is to generate automatic documentation but in the documentation repo

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[github-actions]

This PR exceeds the recommended size of 1000 lines. Check if you are NOT addressing multiple issues with one PR. If is not the case continue the review process.

[johanseto]

I checked the description pr and I like the result, however, there is a misunderstanding since the idea is to generate automatic documentation but in the documentation repo

@andrey-canon I was thinking about integrating this proposal in another way. Please check it and give me your opinion.

https://github.com/nelc/edunext-nelp-documentation/pull/21

In that way, I think all the auto-documentation, at least of docstring, would be updated in the main documentation.