Automatic call of sphinx-apidoc

[sphamba]

Prework

• [x] I understand and agree to this repository's code of conduct.
• [x] I understand and agree to this repository's contributing guidelines.
• [x] I have already submitted an issue or discussion thread to discuss my idea with the maintainers.

What kind of change does this PR introduce? (check at least one)

• [ ] Bugfix
• [x] Feature
• [x] Documentation
• [ ] Tutorial
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes
• [x] No

If yes, please describe the impact and communicate accordingly:

The PR fulfills these requirements:

• [x] It's submitted to the branch named as follow :
  • Fix a bug: bugfix-<some_key>-<word>
  • Improve the doc: doc-<some_key>-<word>
  • Improve a tutorial tutorial-<some_key>-<word>
  • Add a new feature: feature-<some_key>-<word>
  • Refactor some code: refactor-<some_key>-<word>
  • Optimize some code: optimize-<some_key>-<word>
• [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• [ ] Don't forget to link PR to issue if you are solving one.
• [x] All tests are passing.
• [ ] New/updated tests are included

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Related GitHub issues and pull requests

• Ref: #

Summary

• Remove need to run sphinx-apidoc manually
• Remove doc files generated from gpm_api code

[coveralls]

coverage: 0.149%. remained the same when pulling ab0554d02c3abc6cf159984330811a75fc5eb3fd on EPFL-ENAC:feat-auto-code-doc into 179678bf465bead5aa076fade525bf7495e87ee9 on ghiggi:main.