Add instruments to manifest

[MahmoodEtedadi]

Overview

This PR restructures the repository to ensure that all files under the instruments/ folder are included in both the wheel (.whl) and source (.tar.gz) distributions. To achieve this, the instruments/ directory has been moved into src/evaluation_instruments/, making it part of the package namespace and accessible at runtime. The setup.cfg has been updated to include the folder’s contents during wheel builds by configuring the package_data section. Additionally, MANIFEST.in has been revised to explicitly include all relevant file types (such as notebooks, YAML files, and prompts) in the source distribution. These changes ensure that users installing the package from either distribution format receive the full set of required resources.

Description of changes

• Moved instruments/ into src/evaluation_instruments/ to include it as part of the installable package.

• Updated setup.cfg to declare package_data and ensure all files under instruments/ are included in the wheel.

• Added MANIFEST.in to explicitly include all files ininstruments/ (e.g. .ipynb, .yaml, .txt) for source distribution packaging.

Author Checklist

• Linting passes; run early with pre-commit hook.
• Tests added for new code and issue being fixed.
• Added type annotations and full numpy-style docstrings for new methods.
• Draft your news fragment in new changelog/ISSUE.TYPE.rst files; see changelog/README.md.

[diehlbw]

Do we need any changes to the top-level README?
My thought is it would be a description of the vcs-install usecase; especially if calling instruments programatically (not an ipynb) than it may be better to do the pip install git+https (+ tag)

[diehlbw]

the example should probably specify ...evaluation-instruments.git@vX.Y.Z and the text should mention that pinning to a release similarly to pinning a version is recommended

[MahmoodEtedadi]

Updated. We should probably change the convention to vX.Y.Z for future tags. maybe even re-tag 0.0.1.