New readiness checklist

[FabrizioMoggio]

What type of PR is this?

updating the readiness checklist according to the new format define in Release Management (https://github.com/camaraproject/ReleaseManagement/blob/25400e8f484dbb6e53a7dcc21d3a709b6cc2b686/documentation/API-Readiness-Checklist.md)

Add one of the following kinds:

• documentation

What this PR does / why we need it:

To be coherent with the readiness checklist

Which issue(s) this PR fixes:

#34

Special notes for reviewers:

[bigludo7]

Let's wait we're aligned on #42 and this one will be good :)

[FabrizioMoggio]

Let's wait we're aligned on #42 and this one will be good :)

you are totally right :-)

[bigludo7]

We will have to provide links for some of the assets but I guess we can do it later.

[FabrizioMoggio]

We will have to provide links for some of the assets but I guess we can do it later.

once I have produced the release tag we are limited in making change. let me add the links

[rartych]

We will have to provide links for some of the assets but I guess we can do it later.

We can use relative links, that should work with release tags.
https://github.blog/2013-01-31-relative-links-in-markup-files/

[FabrizioMoggio]

We will have to provide links for some of the assets but I guess we can do it later.

We can use relative links, that should work with release tags. https://github.blog/2013-01-31-relative-links-in-markup-files/

I was thinkig of using the same approach as QoD: https://github.com/camaraproject/QualityOnDemand/blob/main/documentation/API_documentation/quality-on-demand-API-Readiness-Checklist.md

not links but a reference to the path

[bigludo7]

LGTM