fix(job_attachment)!: Change osType and source_os names

[gahyusuh]

⚠️ Please use caution before merging, as it requires a preceding change to the backend service model. For more details, please contact @gahyusuh 🙏

What was the problem/requirement? (What/Why)

The field osType: OperatingSystemFamily in job/attachments/manifests is currently being used just to determine how to handle the rootPath (i.e., is it 'posix' or 'windows',) in the API, so it follows more closely with the path mapping rules rather than storage profiles. The field osType in job attachment settings should be renamed to something else, to avoid inconsistencies around the usage of osType, osFamily, and whatever encapsulates 'windows' vs. 'posix' paths.

What was the solution? (How)

• Renamed the field osType: OperatingSystemFamily -> rootPathFormat: PathFormat
• Changed the path mapping rules that are returned from the sync_inputs from source_os to source_path_format

What is the impact of this change?

The field has a better/less-confusing name.

How was this change tested?

• Ran unit tests: hatch run lint && hatch run test
• Ran integ tests: hatch run integ:test
• Ran docker-based tests: hatch run test_docker
• Run an end-to-end test (submitting a non-rendering job bundle --> running a CMF against my local backend)
  • ensuring that there were no issues/errors in the flow.
  • against locally deployed backend, which is (almost) up-to-date at this moment..
  • with the worker-agent changes (fix(job_attachment)!: Change osType and source_os names deadline-cloud-worker-agent#37)

Was this change documented?

No.

Is this a breaking change?

Yes!