Add Object parameters to all the workload yaml files

[FileSystemGuy]

After the v3.0 submission round is over, we should add the Object API parameters to the yaml workload config files for the workloads we're no longer supporting in v3.0, such as unet3d. With that, the community can experiment with Object access in support of those workloads even though we're not using them in the benchmark any longer.

Ie: New DLIO with Object support with the older workload definitions like unet3d.

[FileSystemGuy]

Alternatively, we have talked about regularizing the yaml/json files such that there would be one yaml/json file that defines the workload, one that defines the storage system under test (including mount point or Object API URL), etc.

The value is that:

• The workload params would be isolated from the things the user might want to change
• The SUT values (eg: Object URL) would be common to all workloads
• We would not have a combinatorial explosion of yaml/json files for all supported combinations