feat: persist at version automation support in DB

[stalgiag]

Overview

Moved the "automation support" status for an At Version to the DB. This allows VoiceOver Bot to update the latest supported at version

• Added supportedByAutomation and latestAutomationSupporting boolean columns to AtVersion table
• Backfilled supported versions for VoiceOver, NVDA, and JAWS based on current automation capabilities
• New promoteAutomationSupportedVersion() function to mark a version as latest supported and demote other versions
• VoiceOver jobs automatically promote the new AtVersion when returning a new version from the collection job
• Updated version queries to filter by supportedByAutomation flag instead of hardcoded constants
• Simplified version selection logic to query database directly
• Added tests for new services
• Updated documentation for adding a new at version

[stalgiag]

I accidentally deleted these quotes then thought it was easier to see in my IDE with the descriptor in place

[ChrisC]

@stalgiag I added @howard-e as a reviewer but am curious about what would be the best way to test this manually with a recent data dump from prod? My db dump has some 15.0 automated reruns in the "Automated updates" queue... would I need to ping GH actions and run a job to "promote" a higher version as the latest (e.g. 15.6.1)?

[stalgiag]

That would be the way to test it properly. Most of the time, for quicker testing loops, I was just modifying this line temporarily on my local to force the version name returned from the job to a higher number to simulate running the job on a newer version.