Double check all MR examples

[negz]

• Make sure they're using v2.0.0 providers
• Make sure they use m.example.org style API groups
• Make sure they're namespaced

[netlify]

✅ Deploy Preview for crossplane ready!

Name	Link
🔨 Latest commit	3b49106
🔍 Latest deploy log	https://app.netlify.com/projects/crossplane/deploys/689c3a09a6f6050008d6d070
😎 Deploy Preview	https://deploy-preview-966--crossplane.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 59 (🔴 down 18 from production) Accessibility: 90 (🔴 down 2 from production) Best Practices: 83 (no change from production) SEO: 100 (no change from production) PWA: 70 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[jbw976]

thanks @negz! the only feedback is about the non-upjet provider not having a v2 yet. There's a few places that should be addressed 🙇‍♂️

[negz]

@jbw976 I took another pass, and tried to standardize everything on using the family providers that support v2 style namespaced MRs. I also noticed we needed to update how ProviderConfigs now work.

CC @sergenyalcin @erhancagirici @jeanduplessis - want to take a look at this for accuracy?

P.S. I tested all the (full) example MRs, Providers, and ProviderConfigs against a real kind cluster running Crossplane v2.0.2 (and using v2.0.0 of provider family AWS) to make sure they were schematically valid (i.e. dry run applied successfully).