AP-5647: Update proceeding captions

[colinbruce]

What

Link to story

Switch from proceedings.last to proceedings.order(:created_at).last

Because we use GUIDs as the id, there is no value in a plain .last call as it orders by GUID text. Adding the order allows us to get the most recently created proceeding, which is what is expected, without having to make the URLs and routing more complex by adding specific proceeding IDs into the routes.

This also matches the existing use in the ProceedingIssueStatusesController

Checklist

Before you ask people to review this PR:

• Tests and rubocop should be passing: bundle exec rake
• Github should not be reporting conflicts; you should have recently run git rebase main.
• The standards in the Git Workflow document on Confluence should be followed
• There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
• The PR description should say what you changed and why, with a link to the JIRA story.
• You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
• You should have checked that the commit messages say why the change was made.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[agoldstone93]

This looks like an improvement. Happy to approve. I'm wondering if there's any weirdness when you add and delete proceedings but fingers crossed if there is, it'll come out in UAT

[colinbruce]

This looks like an improvement. Happy to approve. I'm wondering if there's any weirdness when you add and delete proceedings but fingers crossed if there is, it'll come out in UAT

I think it should be okay, because it should always be for the most recently added proceeding, i.e. I have just added X - now ask the question but, as you say, the proof will be in the UAT! 🙂