Add constraint on build number for old ogre builds

[traversaro]

There are some old ogre builds (1.10.12=*_2) that were build without the features required by Gazebo, and that are pulled in when there is some in-progress migration, as they do not have any run constraint on the shared dependencies between Gazebo and Ogre, see:

• https://github.com/robotology/robotology-superbuild/issues/1089
• https://github.com/robotology/gazebo-yarp-plugins/issues/660

• https://github.com/robotology/gazebo-yarp-plugins/issues/664

  To solve this, we can add to gazebo a run constraint to make sure that the ogre version is at least 1.10.12=*_3.

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)
• [x] 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)
• [x] Ensured the license file is being packaged.

[conda-forge-webservices[bot]]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [132]

[conda-forge-webservices[bot]]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [131]

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

[conda-forge-webservices[bot]]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [129]

[traversaro]

I am not sure why the linter is failing, opened https://github.com/conda-forge/conda-forge-webservices/issues/561 to report this.

[traversaro]

Also the build fails with:

Error: Invalid selector in meta.yaml line 130:
offending line:
    - ogre >=1.10.12[build_number=3]

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

[conda-forge-webservices[bot]]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• requirements: run: ogre>=1.10.12[build_number=3] must contain a space between the name and the pin, i.e. ogre >=1.10.12[build_number=3]

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