hit formatting of diemodel input files

[apb13]

Reason

Update input files to align with current hit formatting standards in MOOSE.

Design

Use script capabilities in MOOSE to update hit formatting.

Impact

Increased input file consistency and usability.

[apb13]

Performed comparison between the two csv files, one that was the original and another that received hit formatting, to ensure that the results were the same. Also ensured that comments were formatted correctly in the input file.
Refs #128

[moosebuild]

Job Documentation on d0a7328 wanted to post the following:

View the site here

This comment will be updated on new commits.

[moosebuild]

Job Coverage on d0a7328 wanted to post the following:

Coverage

Coverage did not change

Full coverage report

This comment will be updated on new commits.

[cticenhour]

@apb13 FYI - prior comments made by you can be edited (with version control!). So if you needed to edit the original post, as in this case, you can simply click on the "three dots" on the upper right of any GitHub comment and you'll get the following panel:

Then click on "Edit" to edit the post and click the "Update Comment" button to save!

Just to be clear, you don't need to do this for this PR. I just wanted to share some GitHub tips and tricks for your future PRs!

[sapitts]

@cticenhour do you know what is going on with the Mac test for this PR by chance?

[cticenhour]

We only have a handful of "darwin-clang" (AKA Intel Mac) clients now that the Mac trashcans are no more, so it's likely just busy in the queue.