Add EDOT SDK release notes

[theletterf]

This adds EDOT SDK release notes. To be merged once all tocs are live.

[colleenmcginnis]

Is this blocked until redirects are supported? I don't think we've talked about how to handle redirects when the file paths in the content repos don't change but the path_prefix in navigation.yml changes. 🤔

Edit: Thinking specifically about Android and iOS.

[theletterf]

@colleenmcginnis My gut instinct is to steamroll the old URLs for Android and iOS, since they're so young, and just go with it. The alternative is to keep the old ones till we can do redirects.

[colleenmcginnis]

👍 As long as we're being intentional about it, I think that's fine. A quick search suggests there aren't many (any?) references to the existing /docs URLs.

Although we could request that the redirects for the old AsciiDoc URLs are updated to point to the new URLs since those were more established:

• Android:
  • https://www.elastic.co/guide/en/apm/agent/android/current/release-notes.html → https://www.elastic.co/docs/release-notes/edot/sdks/android
  • https://www.elastic.co/guide/en/apm/agent/android/1.x/release-notes.html → https://www.elastic.co/docs/release-notes/edot/sdks/android
• iOS (these existing redirects are already broken because there are too many redirects so asking to override any existing redirects with this one could be helpful):
  • https://www.elastic.co/guide/en/apm/agent/swift/current/release-notes.html → https://www.elastic.co/docs/release-notes/edot/sdks/ios
  • https://www.elastic.co/guide/en/apm/agent/swift/1.x/release-notes.html → https://www.elastic.co/docs/release-notes/edot/sdks/ios

[theletterf]

Ah, good point about the /guide links! Were shall we ask for those to be implemented?