Breaking changes reference

[cloudjumpercat]

Description

Fixes #549

Preview Links

https://deploy-preview-617--kongdeveloper.netlify.app/gateway/breaking-changes/

Questions for reviewers

• We have a sentence: "We recommend transitioning to OpenTelemetry Instrumentation instead." It originally linked to https://docs.konghq.com/gateway/latest/production/tracing/#main. Should I make a Tracing Reference stub page and link to that instead? It feels like the content on that page should be on the plugins?
• Is there a way (and should we) remove all the headers except the ## [version number] breaking changes headers so it's easier to navigate to the version you need?

Stub pages created:

• Kong Gateway Upgrade reference #619
• How to: Build Custom Docker image #620
• Tracing reference #630

Post GA issue to fix headers:
#631

Checklist

• Every page is page one.
• Tested how-to docs. If not, note why here. N/A: reference
• All pages contain metadata.
• Updated sources.yaml. For more info, review track docs changes
• Any new docs link to existing docs.
• All autogenerated instructions render correctly (API, decK, Konnect, Kong Manager).
• Style guide (capitalized gateway entities, placeholder URLs) implemented correctly.

[netlify]

✅ Deploy Preview for kongdeveloper ready!

Name	Link
🔨 Latest commit	58f2408
🔍 Latest deploy log	https://app.netlify.com/sites/kongdeveloper/deploys/67c9c04cc52aec000889c1a4
😎 Deploy Preview	https://deploy-preview-617--kongdeveloper.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[Guaris]

There isn't much to review here IMO, we just need this page to exist.

It feels like the content on that page should be on the plugins?

I agree, I would add a todo to that page to remind whoever takes that page on to add that info.

Is there a way (and should we) remove all the headers except the ## [version number] breaking changes headers so it's easier to navigate to the version you need?

I think we should. Especially since all of the sections aren't uniform. Personally, I would bold those headers and create a post migration ticket to make these entry uniform if it all possible. There may be a @fabianrbz solution here. I would tag him in it and if there is nothing let's just merge this tomorrow morning.

[fabianrbz]

Is there a way (and should we) remove all the headers except the ## [version number] breaking changes headers so it's easier to navigate to the version you need?

I think we should. Especially since all of the sections aren't uniform. Personally, I would bold those headers and create a post migration ticket to make these entry uniform if it all possible. There may be a @fabianrbz solution here. I would tag him in it and if there is nothing let's just merge this tomorrow morning.

I can't think of anything other than I would bold those headers, manually replace the headers with bold.