chore: Update targeted ODCR to show p5 to be reflect current usage

[bryantbiggs]

Description

• Update targeted ODCR to show p5 to be reflect current usage
  • Remove t3 capacity reservations and require reservation ARN be passed in via variable
  • Show usage with NVIDIA GPU instance and EFA which is the common use case today
• Add pod identity agent - start making it a standard on patterns
• Split out Helm charts to separate file to allow importing into docs site when necessary
• Add kubectl output per usual

Motivation and Context

• While its great to have a pattern that can be deployed and see the reservations, etc. - it did not reflect the current target audience (p4/p5 users with EFA), which led to confusion. This updates the pattern to better reflect what the majority would be using today with capacity allocated in targeted ODCRs (tl;dr - meeting users where they are)

How was this change tested?

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Additional Notes

[bryantbiggs]

not strictly required for this architecture so removing to reduce "noise"

[askulkarni2]

LGTM!