Rebuild for gdal34 and geos3101 in the devel branch

[seisman]

Same as #184 but for the devel branch.

Checklist

• Used a personal fork of the feedstock to propose changes
• 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 @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

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.

[seisman]

@conda-forge-admin, please rerender

[weiji14]

@seisman, do you think we should bump the devel version to GMT 6.4 first? If so, I can open a PR for that, and then have this PR be rebased on top (or just include the version bump directly). Just that I don't see a good reason to have a GDAL3.4/GEOS3.10.1 version of GMT 6.3.0.dev5 when GMT 6.3 stable is out...

[seisman]

do you think we should bump the devel version to GMT 6.4 first? If so, I can open a PR for that, and then have this PR be rebased on top (or just include the version bump directly).

Yes, please open a separate PR bumping the devel version.

[seisman]

Closed by #190.