🎩 What? Why?

There seems to be a consistent issue over the random ordering of records that has had multiple attempts to be fixed in the past (see related issues). The issue still persist.

There seems to be two separate issues related to this as far as I could identify:

1. The random seed is not properly stored in the session variable as I believe was the intention
2. The random order calculation at PostgreSQL can be inconsistent in case any of the the ordered table's records are changed during the user session as explained at Add default order by ID to API list queries #7424.

This fixes both of these issues:

1. The first issue is quite trivial, the value never got stored into the session bag, so fix that.
2. The second issue adds the record IDs as the "base" numbers for the random ordering which should provide more consistent results.

📌 Related Issues

• Related to https://meta.decidim.org/processes/bug-report/f/210/proposals/14295
• Related to https://meta.decidim.org/processes/roadmap/f/122/proposals/15830
• Related to Random order is re-calculated when user goes back to proposals list #5019, Bugfixing #5376, Add default order by ID to API list queries #7424
• (hopefully) Fixes https://meta.decidim.org/processes/roadmap/f/122/proposals/15830

Testing

Describe the best way to test or validate your PR.

📋 Checklist

🚨 Please review the guidelines for contributing to this repository.

• ❓ CONSIDER adding a unit test if your PR resolves an issue.
• ✔️ DO check open PR's to avoid duplicates.
• ✔️ DO keep pull requests small so they can be easily reviewed.
• ✔️ DO build locally before pushing.
• ✔️ DO make sure tests pass.
• ✔️ DO make sure any new changes are documented in docs/.
• ✔️ DO add and modify seeds if necessary.
• ✔️ DO add CHANGELOG upgrade notes if required.
• ✔️ DO add to GraphQL API if there are new public fields.
• ✔️ DO add link to MetaDecidim if it's a new feature.
• ❌AVOID breaking the continuous integration build.
• ❌AVOID making significant changes to the overall architecture.