Update pin for assimp

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update the pin for assimp. The current pinned version is 5.4.3, the latest available version is 6.0.4 and the max pin pattern is x.x.x. This migration will impact 23 feedstocks.

Checklist:

• The new version is a stable supported pin.
• I checked that the ABI changed from 5.4.3 to 6.0.4.

**Please note that if you close this PR we presume that the new pin has been rejected.

@conda-forge-admin please ping assimp

_{This PR was generated by https://github.com/regro/cf-scripts/actions/runs/21350196089 - please use this URL for debugging.}

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/assimp and so here I am doing that.

[conda-forge-admin]

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/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/21350625408. Examine the logs at this URL for more detail.}

[h-vetinari]

We've got the migration for 6.0.3 running already. Let's not do 6.0.4 at the same time (or at all, unless it contains some really important fixes and is actually ABI-incompatible)

[traversaro]

We've got the migration for 6.0.3 running already. Let's not do 6.0.4 at the same time (or at all, unless it contains some really important fixes and is actually ABI-incompatible)

My bad, I merged that PR and I tought assimp was x.x or x, not x.x.x. I think we can go forward with 6.0.3, the changes in 6.0.4 are minimal (and actually abi-compatible in this case).

[h-vetinari]

no need to apologise for merging a version bump. It'd be nice if we wouldn't need to migrate per patch-version though. Is upstream really so ABI-unstable?

[traversaro]

no need to apologise for merging a version bump. It'd be nice if we wouldn't need to migrate per patch-version though. Is upstream really so ABI-unstable?

Apparently I switched to x.x.x in conda-forge/assimp-feedstock#41 and github.com/conda-forge/assimp-feedstock/pull/39 due to an ABI change in assimp/assimp@v5.2.1...v5.2.2 . To be honest I did not tracked the project in recent patches to see if this improved.