eval status: enrich with related evals and placed allocs tables

[tgross]

When debugging an evaluation, you almost always want to know about all the related evaluations and what allocations were placed by that evaluation (and where), not just failed placements. We can enrich the command by adding the related query parameter to the API, and having the command query for the evaluations allocations automatically. Emit this data as a pair of new tables and expose fields like quota limits, and previous/next/blocked eval without the -verbose flag.

Update the docs to include the full output and remove references to long-removed behavior of the -json flag.

Note this PR doesn't include the other NMD-818 work to add reconciler data to the eval status command. That requires scheduler and API changes and will be under another PR.

Ref: https://hashicorp.atlassian.net/browse/NMD-818
Ref: https://go.hashi.co/rfc/nmd-212

Contributor Checklist

• Changelog Entry If this PR changes user-facing behavior, please generate and add a
  changelog entry using the make cl command.
• Testing Please add tests to cover any new functionality or to demonstrate bug fixes and
  ensure regressions will be caught.
• Documentation If the change impacts user-facing functionality such as the CLI, API, UI,
  and job configuration, please update the Nomad website documentation to reflect this. Refer to
  the website README for docs guidelines. Please also consider whether the
  change requires notes within the upgrade guide.

Reviewer Checklist

• Backport Labels Please add the correct backport labels as described by the internal
  backporting document.
• Commit Type Ensure the correct merge method is selected which should be "squash and merge"
  in the majority of situations. The main exceptions are long-lived feature branches or merges where
  history should be preserved.
• Enterprise PRs If this is an enterprise only PR, please add any required changelog entry
  within the public repository.

[tgross]

Note to reviewers: this test change only exists for me to verify that we avoid overwriting query params with QueryOptions, and I left it in to document the behavior.

[tgross]

Note to reviewers: as part of NMD-818 I'm planning on some follow-up here, in the API docs, and in the alloc status docs to describe a lot of this more fully. But that'll be under a separate PR.

[jrasell]

LGTM!