Feature 2741 running metplus

[lisagoodrich]

Pull Request Testing

• Describe testing already performed for these changes:
  
  This portion of the pull request cleaned up the "Running METplus" Use Case section.

1. I cleaned up the extraneous language and matched the text to the Use Case Template.
2. I removed any instance of "-c " which is no longer an applicable command. These were found by running the command, "find . -name "*.py" | xargs egrep -n "-c " | more" in the model_applications folder. Please note that @CPKalb is working on the majority of the s2s Use Cases and are not included with this pull request.
3. Please note, in some cases the "-c" was found in the METplus Configuration section. I removed the "-c" and did my best to update the language to the template.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  This task was straightforward to complete. Please review for anything I might have overlooked. There are no questions for review on the spreadsheet. Here is a link to the web pages. I think I got all of the commas, but feel free to double check.

DO NOT CLOSE THIS ISSUE when the pull request is completed. There is more work to be done on this issue.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]

• Do these changes include sufficient testing updates? [Yes]

• Will this PR result in changes to the test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Do these changes introduce new SonarQube findings? [No]
  
  If yes, please describe:

• Please complete this pull request review by [11/22/24].
  

Pull Request Checklist

See the METplus Workflow for details.

• Add any new Python packages to the METplus Components Python Requirements table.
• For any new datasets, an entry to the METplus Verification Datasets Guide.
• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the version that will include these changes
  Select: Coordinated METplus-X.Y Support project for bugfix releases or METplus-Wrappers-X.Y.Z Development project for official releases
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[jprestop]

Thanks for all of your work on this task @lisagoodrich. Looks good! I'll go ahead approve and Squash and Merge. I will leave the branch alone for now and will also leave the issue open.

[lisagoodrich]

@jprestop thank you so much for explaining why and what needed to be changed. I've removed all of the "literalinclude: bash" references. I think it's good to go. Let me know if you find other problems. Thanks!