Cleanup/Alignment of submission structure

[pgmpablo157321]

• The submission directory has five specified directories, and these remain sufficient to organize the necessary data (“A submission should take the form of a directory with the following structure. The structure must be followed…”). For many rounds however, vendor harnesses have unnecessarily expanded far beyond this structure with vendor-specific scripts, config details, environment, and documentation. Though the original intent may have been benign, the result is to make one vendor ubiquitously represented across nearly all submitter content (see image below) and to clutter the defined structure.
• There are several potential solutions to alleviate such concerns. However the most straight-forward are:
  • As the code is nearly identical across OEMs, the vendors need only reference the original vendor code. This is the existing Intel approach.
  • A vendor can create a dir such as ‘{SUBMITTER}/code/nv_harness’ to contain all the extra content currently residing in the ‘{SUBMITTER} dir.
• In the case where harness-specific documentation is replicated in OEM ‘common’ locations (ex. here or here), name files in such a way that the scope is clear (ie. calibration.md -> calibration.nv.md or nv/calibration.md).
• This issue was initiated in v4.1 post-mortem, but tabled with plans of offline resolution. No further action has been taken.

Post mortem task proposed by @keithachorn-intel

[keithachorn-intel]

PR created to highlight the intent of aligning to the outlined directory structure.

[hanyunfan]

Closing since the discussion has moved to policies#195