Features/505 fix cross environment database backup

[naomitodd]

Description

Update to original backup & restore workflow - now uses github artifacts to share backup file between azure subscription environments.
Increase timeouts and chunk restore job with retries similar to data pipeline to combat lost connection errors.

https://trello.com/c/rX9Ldere/505-look-into-how-we-can-push-data-to-production-without-wiping-the-gateway-users

Will raise placeholder tickets to look into amendments to data pipeline to allow safe running into production environment as an ideal production-ready solution:

• can't reproduce but saw some duplicate edubase tables when restoring backups due to naming conventions maybe? tables not being dropped - shouldn't affect views as they are rebuilt but possibly storing unneeded data by not fully refreshing the data
• need to action ticket to reduce data ingestion / may be addressed slightly by EES changes
• amend to only update changed data or files?
• add db unit testing for confidence (see data engineer review)
• add smoke tests to pipeline
• add maintenance page triggers to data pipeline
• consider how data is managed for publication releases?
• full overhaul of data ingestion unlikely?

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Tested cross environment
Prod > Test- https://github.com/DFE-Digital/sap-public/actions/runs/26044867072
Test > Prod - https://github.com/DFE-Digital/sap-public/actions/runs/26080886079
confirmed manually gateway users unaffected

[github-actions]

Code Coverage Report: Only Changed Files listed

Package	Coverage
Overall Coverage	🟢 60.23%

Minimum allowed coverage is 0%, this run produced 60.23%

[DMurf]

Looks okay to me, happy to merge and give it some time to bed in :)