Test entry points, call all Python apps with --help

[plimkilde]

Checklist

• [X] Used a personal fork of the feedstock to propose changes
• [X] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

Closes #834

Now that GDAL 3.9 has landed, we can test the proper entry points (Python apps, called without the .py extension). Also incorporated are changes (as a result of upstream GDAL fixes) so that all of these apps are now tested with --help, see https://github.com/OSGeo/gdal/issues/8717.

There has been a bit of churn on GDAL upstream regarding these entry points, see:

• https://github.com/OSGeo/gdal/pull/8718
• https://github.com/OSGeo/gdal/pull/8774
• https://github.com/OSGeo/gdal/issues/8811
• https://github.com/OSGeo/gdal/pull/8815
• https://github.com/OSGeo/gdal/pull/8824

The commands including .py are still the ones shown in GDAL docs, so for now I test both e.g. gdal_calc.py and gdal_calc.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[gillins]

Thanks @plimkilde @rouault this is a huge step forward and will definitely make life much easier!

[plimkilde]

Rebased to fix build number conflict