_ in type for data and change to data_big

[kellijohnson-NOAA]

What is the feature?

• Change all type names to use underscores in the stored data, e.g., weight_at_age
• Use a stored object fims_input_types to check the validity of input types that are present
• Change data1 to data_big because Andrea will have a data_limited later for the surplus production model and Ian has a data_small in PR Add data_small dataset and associated test and documentation #958
• Add test coverage for R/fimsframe.R

Does the PR impact any other area of the project, maybe another repo?

• Yes, the case studies will need to be updated
• @iantaylor-NOAA function for converting SS3 data in {r4ss} will need to be updated to produce type names with underscores

Close #1247

---

Instructions for code reviewer

Hello reviewer, thanks for taking the time to review this PR!

• Please use this checklist during your review, checking off items that you have verified are complete, but feel free to skip over items that are not relevant!
• See the GitHub documentation for how to comment on a PR to indicate where you have questions or changes are needed before approving the PR.
• Please use conventions in the guidelines for conventional commit messages for both commit messages and comments.
• PR reviews are a great way to learn so feel free to share your tips and tricks. However, when suggesting changes to the PR that are optional please include nit: (for nitpicking) as the comment type. For example, nit: I prefer using a data.frame() instead of a matrix because ...
• Engage with the developer when they respond to comments and check off additional boxes as they become complete so the PR can be merged in when all the tasks are fulfilled. Make it clear when the PR is approved by selecting the approved status, and potentially by commenting on the PR with something like This PR is now ready to be merged, no additional changes are needed.

Checklist

• The PR is requested to be merged into the appropriate branch (typically dev).
• The code is well-designed.
• The functionality is good for the users of the code.
• Code coverage remains high, indicating the new code is tested.
• The code is commented and the comments are clear, useful, and mostly explain why instead of what.
• Code is appropriately documented (doxygen and roxygen).

[codecov]

Codecov Report

❌ Patch coverage is 92.95775% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.91%. Comparing base (ab0b19f) to head (c57b896).
⚠️ Report is 3 commits behind head on dev.

Files with missing lines	Patch %	Lines
R/fimsframe.R	92.64%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1293      +/-   ##
==========================================
+ Coverage   86.87%   88.91%   +2.04%     
==========================================
  Files          81       80       -1     
  Lines        7803     7923     +120     
  Branches      496      538      +42     
==========================================
+ Hits         6779     7045     +266     
+ Misses       1019      854     -165     
- Partials        5       24      +19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.