Add exodus library from SEACAS

[rfiorella]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• 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.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-admin]

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 (recipes/seacas-exodus/meta.yaml) and found some lint.

Here's what I've got...

For recipes/seacas-exodus/meta.yaml:

• ❌ The "test" section was expected to be a dictionary, but got a NoneType.
• ❌ The recipe must have some tests.
• ❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [15]
• ❌ The "test" section was expected to be a dictionary, but got a NoneType.
• ❌ The "test" section was expected to be a dictionary, but got a NoneType.

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

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[rfiorella]

@conda-forge/help-c-cpp SEACAS is also distributed with trilinos. The current trilinos feedstock is quite old (I'm working on fixing that), but I'm wondering if in these cases there would be a recommendation to just use trilinos to get the exodus libraries or whether there's a benefit in having a smaller package for people that only need exodus and not all of the various trilinos packages

[danielnachun]

You should see if you can create multiple outputs for the trilinos feedstock in that case. One of the package outputs can be the "full" trilinos installation with all the other packages as dependencies for users that need all of trilinos, and the individual packages would then be installable as standalone packages as well.