post v5.3.0 release chores

[charleenfei]

updates the compatibility test matrices and e2e simd and icad workflows

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (see CONTRIBUTING.md).
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/) or specification (x/<module>/spec/).
• Added relevant godoc comments.
• Provide a commit message to be used for the changelog entry in the PR description for review.
• Re-reviewed Files changed in the Github PR explorer.
• Review Codecov Report in the comment section below once CI passes.

[crodriguezvega]

Thank you, @charleenfei; and great that these changes can be automated now! 🤖

I think we are missing a couple of though:

• Updating the changelog with the entries for the v5.3.0 release.
• Updating RELEASES.md with the new supported release line and the versions of dependencies use in v5.3.0.
• Adding the new release to the docs site.

[charleenfei]

Thank you, @charleenfei; and great that these changes can be automated now! 🤖

I think we are missing a couple of though:

• Updating the changelog with the entries for the v5.3.0 release.
• Updating RELEASES.md with the new supported release line and the versions of dependencies use in v5.3.0.
• Adding the new release to the docs site.

hi! i did update the CHANGELOG on the v5.3.x line, should I update it on main as well? I also updated the RELEASES.md here.

[charleenfei]

regarding the docs, i was waiting for the large bulk of docs migrations work from @srdtrk to stabilise, but it looks like he's already added v.5.3 here

[crodriguezvega]

i did update the CHANGELOG on the v5.3.x line, should I update it on main as well?

Yes, I would also update main with the changelog for v5.3.0.

I also updated the RELEASES.md here

Cool. I didn't see that it was done separately.

regarding the docs, i was waiting for the large bulk of docs migrations work from @srdtrk to stabilise, but it looks like he's already added v.5.3 here

Maybe we could still update the existing website, since the new docusaurus site has not been deployed yet, right?

[damiannolan]

what does this file do? or where is it used?

[srdtrk]

It is used to generate the old docs (tells docs to pull docs from this version's github tag too)