Fix issue with rate limiting and expired applications

[kylesoskin]

Summary

• This adds the option to instantiate a backup submission object without automatically requesting an upload UUID from lighthouse, this eliminates the 429/ratelimit when doing batch processing
• This also fudges the expiration date to allow a doc to be generated through EVSS, the date is not actually used by them for anything, confirmed by EVSS so fudging it does not effect anything, except lets it go through to PDF generation, which is what we want
• This is owned by Benefits Team 1 or Decision Review Team
• no flipper

Related issue(s)

department-of-veterans-affairs/va.gov-team#50111

Testing done

-locally, rspec, will do staging once merged

What areas of the site does it impact?

*backend and sidekiq

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature