Add the ability to configure the cyhy-commander's next-scan-limit value

[mcdonnnj]

🗣 Description

This pull request adds the ability to configure the next-scan-limit value in the cyhy-commander configuration file.

💭 Motivation and context

We want to update the value being deployed in production but rather than continuously modifying a hard-coded value it made sense to integrate this as a configurable value between the Ansible role and the Terraform configuration.

🧪 Testing

Automated tests pass locally. Tests on GitHub will require final resolution of #661 and integration in this branch to pass. I deployed this in my development environment with a non-default value and confirmed it deployed successfully.

✅ Pre-approval checklist

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

[dav3r]

This all works for me! 🖖

I noted a nitpick, but feel free to ignore.

[mcdonnnj]

@jsf9k @dav3r I modified this after looking at it again to change the production section instead of the DEFAULT section. I think this better aligns with what is intended and will also align with future updates to allow further customization through the Terraform configuration.

[dav3r]

👍 👍