As a user, I want to see API stable release specifications

[tloubrieu-jpl]

💪 Motivation

...so that I can see not only the specification under development but also the latest stable releases and the previous ones.

📖 Additional Details

The requires:

• propose an organization of the website enabling multiple versions nasa-pds.github.io/pds-api
• implement the stable release github action

Keep an opening on how to combine multiple application API (e.g. registry + doi)

⚖️ Acceptance Criteria

Given a stable release of the API specification
When I perform a request on url http://nasa-pds.github.io/pds-api/{to be defined, contains X.Y.Z}
Then I expect I can see the stable API specification X.Y.Z

Given
When I perform a request on url http://nasa-pds.github.io/pds-api/
Then I expect I can see pointer to all the history of pds API specifications

⚙️ Engineering Details

[tloubrieu-jpl]

Now the API specifications are presented in a sphinx read the doc web site on gh-pages.

Every applications (registry, doi) and version are stored in a single directory (specs) and the documentation can be generated automatically.

The standard roundup cicd should work (not tested since we are on a feature branch).