Provide more context for breaking changes links

[karenzone]

PREVIEW: https://stack-docs_1784.docs-preview.app.elstc.co/diff

Our breaking changes content in the Installation and Upgrade Guide could use a bit more context around the links.

At first glance, this link appears to be self-referential, when in fact, it's sending the user to the Logstash Reference. I know this content well, and still had a "where the heck am I" moment. This could have implications for screen readers as well.

I made a proposal for Logstash (and for other books as well) to add a clue that the link will send you to another book.

You get to decide for your deliverables

Like your links they way they are now? Prefer a different approach? Let me know, and we can make the change in this PR, or reverse the change for your docs.

Another thought

The breaking changes for Logstash are identical between the Installation and Upgrade Guide and the Logstash Reference. Is this statement true for other products?

I'm considering changing the text to something like "The list of breaking changes is also available in the Logstash Reference" to avoid sending users away for more info when there isn't any additional info.

[karenzone]

@lcawl I've tagged you for initial discussion.
@everyone I welcome your input as well -- now or later.

[lcawl]

Theoretically the addition of book names is applicable only until we migrate (and no longer have books, hooray). But then again, I'm also hoping the elastic.co/new project will render these repeated highlights and breaking changes unnecessary by then, so let's do whatever helps here now. LGTM

[karenzone]

I went down the same thought path. We new docs system and new release notes initiative should solve these problems, but that's no reason not to mitigate them for the present. Thanks!

[mergify]

This pull request is now in conflict. Could you fix it @karenzone? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b bc-text <remote-repo>/bc-text
git merge <remote-repo>/main
git push <remote-repo> bc-text

[mergify]

This pull request does not have a backport label. Could you fix it @karenzone? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-/d./d is the label to automatically backport to the /d./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[mergify]

This pull request is now in conflict. Could you fix it @karenzone? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b bc-text <remote-repo>/bc-text
git merge <remote-repo>/main
git push <remote-repo> bc-text

[mergify]

This pull request is now in conflict. Could you fix it @karenzone? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b bc-text <remote-repo>/bc-text
git merge <remote-repo>/main
git push <remote-repo> bc-text

[mergify]

This pull request is now in conflict. Could you fix it @karenzone? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b bc-text <remote-repo>/bc-text
git merge <remote-repo>/main
git push <remote-repo> bc-text

[mergify]

This pull request is now in conflict. Could you fix it @karenzone? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b bc-text <remote-repo>/bc-text
git merge <remote-repo>/main
git push <remote-repo> bc-text