Contributing adjustments

[iainDe]

🗣 Description

💭 Motivation and context

🧪 Testing

✅ Pre-approval checklist

• [x] This PR has an informative and human-readable title.
• [x] Changes are limited to a single goal - eschew scope creep!
• [x] All future TODOs are captured in issues, which are referenced in code comments.
• [x] All relevant type-of-change labels have been added.
• [ ] I have read the CONTRIBUTING document.
• [ ] These code changes follow cisagov code standards.
• [x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• [ ] Tests have been added and/or modified to cover the changes in this PR.
• [x] All new and existing tests pass.

✅ Pre-merge checklist

• [ ] Revert dependencies to default branches.
• [ ] Finalize version.

✅ Post-merge checklist

• [ ] Add a tag or create a release.

[iainDe]

Let me know if this is satisfactory documentation to future contributors. From the CONTRIBUTING.md users would navigate the link to PULL-EXAMPLE.md

[iainDe]

I would suggest this section could be removed:

"Note: we are tracking multiple CVEs on the backend but are currently only displaying all the CVE-2021-44228. The multiple CVEs will not be listed in the table per the current request, instead the logic will determine and present a single status based on the available data in the template. "

That was included in the notes for context, but we probably don't need to keep it in the contributing doc - especially if we are expecting there may be some PRs for the other related CVEs moving forward.

The reporter field should also be removed from the template and example, since this field will be machine generated moving forward: " reporter: cisagov"

@chelsgr Changes made as suggested to the PULL-EXAMPLE.md. Eliminated the comment on tracking CVEs on the backend, and removed the two instances of the reporter being a tracked field. Feel free to make the Merge when appropriate