Repurpose dispatch-job capability to dispatch periodic jobs

[notnoop]

This PR repurpose dispatch-job for periodic job force invocation in addition to parameterized jobs.

Currently, force evaluating a periodic job requires submit-job capability, a too powerful capability as it allows submitting arbitrary jobs to the cluster. In contrast, submitting a new parameterized job require submit-job capability, but manually invoking it only requires dispatch-job. Having a lower-scoped capability allow delegating debugging or recovery handling to operators or tools with less privileges.

I've considered introducing a new capability just for periodic jobs, but I thought such fine-grain capability seems unwarranted. In both the periodic and parameterized job, we'd want operators to invoke jobs that are already registered and allowed in the cluster.

Closes #7703

[schmichael]

LGTM. Don't forget to update docs:

• changelog
• https://www.nomadproject.io/api-docs/jobs#force-new-periodic-instance

[notnoop]

Thanks! Updated changelog and docs!

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.