CSI: add missing plugin capabilities to api response

[tgross]

Detection of the full set of plugin capabilities was added in Nomad
1.1 for the volume creation workflow, but these were not added to the
API response for plugins.

Blocks showing caps in plugin status -verbose #10221
Nice-to-have for implementing topology in #7669

[DerekStrickland]

My one comment would be that some field names are camel cased versions of the full setting name and some are partial. For example, if you had SETTING_NAME sometimes the field is SupportsSettingName and sometimes it's SupportsSetting. Not a blocker, but I think it is less ambiguous to use the full setting name, and also helps guard against name collision or prefix reuse upstream that we may not have control over. I realize it's verbose, but that my 2 cents.

[tgross]

My one comment would be that some field names are camel cased versions of the full setting name and some are partial.

I don't disagree and in retrospect I think I probably would have returned a list of these instead of bools anyways. Way-back-when we'd decided we were definitely not going to support create volume, but then came back months later and did it anyways, but by then we had the bool fields and it got pretty gory. 🤣

But in any case, here I'm actually matching the field names from the existing structs version of the same fields (ex structs.CSIContollerInfo), and we don't want to differ between them so that serialization works without having to write it all by hand.

[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.