docs: fix kustomize patches example

[morey-tech]

Related to: #16352 Also, add an ApplicationSet example.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ae07eb6) 49.55% compared to head (4ebd64a) 49.55%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #16353   +/-   ##
=======================================
  Coverage   49.55%   49.55%           
=======================================
  Files         269      269           
  Lines       47039    47039           
=======================================
  Hits        23310    23310           
  Misses      21443    21443           
  Partials     2286     2286           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[alexmt]

Thanks for fixing the example!