Vitis 13804 : XRT-SMI re-architecture Patch 1

[aktondak]

Problem solved by the commit

This PR is the first in a series of PRs to follow for https://jira.xilinx.com/browse/VITIS-13804 and xrt-smi re-architecture.
This PR does the following :

1. Introduces a new class hierarchy(SubCmdJsonObjects) to store xrt-smi specific configuration data (queried from shim through a device query).
2. Edits the SubCmdValidate class to use above architecture to add program options at run-time using the conf contents.

What's next ?

1. Other xrt-smi SubCommands (examine and configure) will follow suit to use the Json configuration for program option addition making xrt-smi scalable and conforming to device specific Jsons.
2. Currently, the help printing still relies on program option addition. That will be removed based on the contents of the conf.

Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered

https://jira.xilinx.com/browse/VITIS-13804 partially

How problem was solved, alternative solutions (if any) and why they were rejected

The problem was solved by coming up with a Json Schema and conforming to that when writing the SUbCmdJsonObjects classes.

Risks (if any) associated the changes in the commit

xrt-smi validate should be tested further since this changes the existing behavior.

What has been tested and how, request additional testing if necessary

Tested xrt-smi validate on windows and Linux platforms.

Documentation impact (if any)

N/A

[gbuildx]

Can one of the admins verify this patch?

[rchane]

After initial discussion, this PR seems good to me for our first step of re-architecture once it is ironed out and passes pipeline.

[AShivangi]

let's remove m_ in the next iteration of changes

[AShivangi]

Looks good for the first iteration! Let's get this in asap so we can start some bash testing