Re-render after gcc and clang update and bump version to 1.6.0

[traversaro]

gcc was updated from 11 to 12 and clang was updated from 14 to 15 in conda-forge/conda-forge-pinning-feedstock#4215, this re-render propagates the same change to the compilers package.

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-webservices]

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.

[traversaro]

This supersedes #57 .

[traversaro]

@conda-forge/compilers the PR is ready for review, thanks!

[traversaro]

@conda-forge/compilers the PR is ready for review, thanks!

@conda-forge/compilers feel free to let me know if there is anything I can do to help the review of the PR, thanks!

[isuruf]

Waiting until conda-forge/clangdev-feedstock#213 is resolved.

[traversaro]

I see, thanks for the feedback.

[traversaro]

To get at least gcc 12, would it be ok if I pinned manually clang on macOS to 14, and then we can remove the pin once/if conda-forge/clangdev-feedstock#213 is solved? This may be also a bit more robust against someone accidentally merging a rerender in another PR to this repo.

[isuruf]

Thanks

[traversaro]

Thanks

Thanks for merging!