[FFS-4381] switch to an autogenerated swagger approach

[iannorriswork]

Jira Ticket

• FFS-4381

Description

This is a PR trying to move away from handcrafted swagger towards something that actually lives in the code.

• generate the swagger from Rails
• uses tests to enforce that the swagger is being updated continuously
• if this looks good, will apply to the other endpoints as well.
• the one annoying thing in this is having to switch from minitest to Rspec, though I do think Rspec is superior anyway.

Submitter Checklist

• Jira Ticket: The relevant Jira ticket is linked in the header.
• Evidence of Testing: I have included evidence of bench testing (e.g., terminal output, screenshots, logs) below.
• Security Boundary: I have checked if any security boundaries are changing.
  • If yes, I have pointed to the relevant Security Impact Analysis (SIA) or escalated to the security team.
• Backwards Compatibility: I have verified that these changes do not introduce any backwards compatibility issues.
  • [] If no, I have added appropriate new versions or feature flags and flagged the team and appropriate stakeholders
• I've updated the Confluence documentation, content in the /docs folder, and any API spec docs

Reviewer Checklist

• Verification: I have verified that the changes work as intended.
• Backwards Compatibility: I have confirmed that the code does not introduce any backwards compatibility issues.
• Security & Privacy: I have reviewed the changes for potential security or privacy risks (e.g., PII handling).
• Contract Compliance: If the public API contract changed, I have verified that it is reflected in api-spec/ and follows the organization's standards.
• Code Quality: The code is clean, well-tested, and follows the established patterns in the codebase.
• Code Quality: The code has unit and integration tests that cover relevant code changes.

Evidence of Testing

Paste test results here

[tdooner]

Seems legit but, oh man, what is going on with all that stubbing in rails_helper.rb?

[tdooner]

Huh what, is there really no better way to stub out whatever AWS is necessary for (publishing the swagger file?) than this? Can we just disable the AWS related thing in test?

[iannorriswork]

yeah, that was the AI fighting against some defaults i need to fix...i'll yank that out and go fix that seperately.