Contradictory noarch: python lints

[isuruf]

For recipes/organizeit2/recipe.yaml:

    ❌ noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

For recipes/organizeit2/recipe.yaml:

    ℹ️ noarch: python recipes should usually follow the syntax in our [documentation](https://conda-forge.org/docs/maintainer/knowledge_base/#noarch-python) for specifying the Python version.
        For the host section of recipe, you should usually use python ${{ python_min }} for the python entry.
        For the run section of recipe, you should usually use python >=${{ python_min }} for the python entry.
        For the test.requires section of recipe, you should usually use python ${{ python_min }} for the python entry.
        If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

See conda-forge/staged-recipes#29047 (comment)

cc @ocefpaf, @beckermr

[ocefpaf]

I believe that only happens in v1 recipes, right?

[beckermr]

The lint text needs to be updated, but otherwise the two items are not in conflict. We do require a lower bound on the python version at runtime for noarch packages and also it should usually use the python_min variable, but it does not have to.