Update the unit test diff logic to handle SEEPS, SEEPS_MPR, and MODE CTS line type updates

[JohnHalleyGotway]

Describe the Task

The SEEPS and SEEPS_MPR line types were added in MET version 11.0.0 but never added to the differencing logic for the MET unit tests. While that differencing logic will be replaced by a python version, this is an easy issue to add these line types to the existing logic so that it is available to be ported over. Only need to update the develop branch but add SEEPS and SEEP_MPR entries to the header table files for 11.0.0, 11.1.0, and the upcoming 12.0.0.

Note that 7 new columns are also added to the MODE CTS output line type for 12.0.0. However, the column header table files have not yet been updated to reflect those changes.

Time Estimate

1 hour

Sub-Issues

Consider breaking the task down into sub-issues.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as the next official version or Backlog of Development Ideas
• For the next official version, select the MET-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy
  None.

Task Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the next official version
  Select: MET-X.Y.Z Development project for development toward the next official release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.