Possible to specify static libraries for package_contents?

[matthewfeickert]

In the package_contents tests, the lib key only checks for dynamic libraries

rattler-build/docs/testing.md

Line 98 in 08f81cf

- **`lib`**: matches libraries in the package (`.so`, `.dll`, `.dylib` files). The test fails if any of the libraries are not found. It's enough to specify the library name without any extension (e.g. `foo` will match `libfoo.so`, `libfoo.dylib`, and `foo.dll`).

As there are times when static libraries need to be packaged in conda packages, is it possible to indicate this as a subkey in lib? (Currently it seems like "no" and you need to use the files key to test for the existence of static libraries.) If not, would this be something that could be added?

• This is in a related, but different, direction as feature request: SOVERSION check in package_contents #1217
• c.f. MNT: Update to v1 recipe conda-forge/qcdloop-fortran-feedstock#2 for use example.