Handle simultaneous update and deprecate/restore

[MJGaughran]

At the moment, if you update a Module's contents as well as deprecate or restore it, only the update takes effect on sync. This means that the compare command will fail the next time it is run, as the modulefile is not in the correct location.

This only needed a fix to validation as deploy was already capable of handling Modules that fell into more than one category.

When creating the tests, it was clear that some places used "active" and others "live" to refer to a non-deprecated module, so I have cleared this up.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.48%. Comparing base (4f5ee44) to head (08fde82).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
- Coverage   99.48%   99.48%   -0.01%     
==========================================
  Files          27       27              
  Lines         979      978       -1     
==========================================
- Hits          974      973       -1     
  Misses          5        5              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ptsOSL]

Looks good to me.

Out of curiosity, is it possible to create a new release with deprecated=true? And could this cause issues

[MJGaughran]

Looks good to me.

Out of curiosity, is it possible to create a new release with deprecated=true? And could this cause issues

You can with --from-scratch or --allow-all.

We don't explicitly test it for a new deployment, but as --from-scratch implies --allow-all, this particular case is covered in the test: https://github.com/DiamondLightSource/deploy-tools/blob/main/tests/test_validate.py#L82