(Closes #3364) Prepare for release 3.3.0

[arporter]

Just updates the version number in the two locations.
At merge time we'll need to update the changelog too.
As the 'update to fparser 0.2.4' has just gone on, we know that all of the fparser settings in the various workflow files are correct already.

[arporter]

Ready for review (@hiker or @sergisiso) and for final testing at the Met Office (@andrewcoughtrie). Sergi tells me that he's also brought the associated lfric_apps PR up-to-date: MetOffice/lfric_apps#545

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (4216b9a) to head (530f770).

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3470   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          395       395           
  Lines        55199     55199           
=========================================
  Hits         55199     55199           

☔ 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.

[sergisiso]

@arporter Since this cycle we moved to pyproject so I attempted the build manually and everything worked, but it has the same warning that we fixed in fparser:

SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated
!!

        ********************************************************************************
        Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0).

        By 2027-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

Could you fix it here as well please?

[sergisiso]

It's a bit unfortunate that we have to move a number down. How did that happen? Was it because we did a release candidate and didn't do the associated release?

[arporter]

Yes. We did the rc release and then I bumped the working version to 3.3.1-dev. In retrospect this should probably have been 3.3.0-rc2-dev.

[arporter]

(I was expecting that we'd make the release shortly after the rc but in the end, it didn't make sense to do that.)

[arporter]

License string updated (GH wouldn't let me respond to the comment directly) and I've pushed the changes.
Ready for another look/to hear back from the MO.