Add mrio_common_metadata

[xylar]

Checklist

• [x] Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• [x] License file is packaged (see here for an example).
• [x] Source is from official source.
• [x] Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• [x] Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• [x] Build number is 0.
• [x] A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• [x] GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• [x] When in trouble, please check our knowledge base documentation before pinging a team.

[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 (recipes/mrio_common_metadata) and found it was in an excellent condition.

[xylar]

@conda-forge/help-python, this is also ready to review. Thank you in advance!

[xylar]

@chrisburr, you kindly reviewed other Brightway-related recipes recently. https://github.com/conda-forge/staged-recipes/pull/19941 https://github.com/conda-forge/staged-recipes/pull/19944 https://github.com/conda-forge/staged-recipes/pull/19946 Would you have time to review this one as well? It is a dependencies of other recipes that @cmutel would like to get in.

[xylar]

@conda-forge/help-python, we've been waiting on a review here for about 2 weeks now. Any chance of getting one?

[xylar]

Thanks @chrisburr!

@cmutel, I think you wanted to do the next round of recipes yourself. Just ping me if you want help or if you want to include me as a maintainer.