feat!: prep for rootPathFormat becoming ALL UPPERS

[epmog]

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

API model for rootPathFormat is changing from lowercase to uppercase, so we need to prep ahead of time so that we support both when the swap happens.

What was the solution? (How)

• Re-added the shim to deadline.client to ensure that create_job uses the correct version of rootPathFormat.
• Modified deadline.job_attachments to switch the enum to ALL UPPERS, and if the enum can't be found (ie. windows) that it would see if the uppercase version exists.
• get_job is also affected, but we only use this on download, so we can just swap that usage to ALL UPPERS all the time.
• Downstream dependencies worker agent and openjd handle PathFormats regardless of lowers or uppers (they use uppers), so this doesn't actually break them.

What is the impact of this change?

• If a model exists that uses lowercase enums, it will use that on create_job
• Regardless of what model exists for get_job, it'll work.

How was this change tested?

Added tests around the _missing_ feature of the enum, as well as the DeadlineClient create_job shim

hatch run fmt
hatch build
hatch run lint
hatch run test

I then attempted to submit job bundles using the old model, and confirmed that it changed the request to use the lowercase version.

Was this change documented?

N/A

Is this a breaking change?

This is a breaking change since we're changing the PathFormat enum's values and the format of the strings returned for the path mapping rules in sync_inputs (even though the only known dependency handles this already).

[ddneilson]

We're sure that this one is changing? Things are moving quick, so it's not clear to me.

[marofke]

🚢 🦈