drivers: include volume within mount config

[chrisroberts]

Description

Add an optional RequestName attribute to the mount config. If the mount config entry originated from a volume, the request name of the volume from the job spec will be included within the entry.

This modification is useful for drivers that may want to provide special handling of volumes. Including the volume name (if applicable) allows plugin configuration to reference the volumes and associate them to the correct mount configuration entries.

Testing & Reproduction steps

Links

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 product documentation, which is stored in the
  web-unified-docs repo. Refer to the web-unified-docs contributor guide for docs guidelines.
  Please also consider whether the change requires notes within the upgrade
  guide. If you would like help with the docs, tag the nomad-docs team in this PR.

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.

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

[tgross]

LGTM!

I suspect down the road we're going to want to stick more metadata about the volume we have on this struct, like the volume ID or source ID (from CSI), etc. We'll probably want to have some subset that we put on the request object itself as you've done here and then have a map of misc labels or whatever. But that's for future work!

[tgross]

LGTM