Fix and test containers

[ColmTalbot]

The CI tests are pretty broken again. I'm not sure if this is due to changes I made or not.

I added some tests to the containers between building and pushing them, so hopefully we won't have broken containers being pushed in the future.

Summary of changes:

• the dockerfile gets SETUPTOOLS_SCM_IGNORE_DUBIOUS_OWNER=1. This tells setuptools_scm to ignore the fact that it is being run in a repository the user doesn't own.
• the containers are stored to local storage after being built.
• these local containers run the basic tests (imports and entry points).
• if these tests pass, the last stage uploads the containers to the registry.

I don't understand why the user doesn't own the repository anymore, but this fixes the problem at least.

As usual, if this isn't merged by midnight the old container will be rebuilt and things will start breaking again.

I also reactivated the tests that our command line entry points work.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.24%. Comparing base (cde65c5) to head (8ad24e9).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1067   +/-   ##
=======================================
  Coverage   66.24%   66.24%           
=======================================
  Files          89       89           
  Lines       17064    17064           
  Branches     2642     2642           
=======================================
  Hits        11304    11304           
  Misses       5021     5021           
  Partials      739      739           

Flag	Coverage Δ
python310	66.03% <ø> (-0.05%)	⬇️
python311	66.24% <ø> (+0.03%)	⬆️
python312	66.19% <ø> (-0.05%)	⬇️
python313	66.19% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 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.

[ColmTalbot]

The latest jobs are failing because:

• the py310 container doesn't contain the setuptools fix. I think this means it is not to do with a change in the build as we haven't rebuilt this container for a while.
• python312+ is using arviz=1 which chnaged the API pretty heavily. I'm going to pin that in the environment file.

[GregoryAshton]

I read over the MR and it looks good to me.