fix configuration file links

[christinaausley]

Description

Relates to #3744.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @christinaausley as a reviewer.

[akeller]

Thanks for fixing this per version! Can you add a reminder to update the link when we cut the docs release for 8.6?

I thought there was something in the backlog for exploring variables for this, but I'm not seeing anything.

[falko]

Micro releases should usually not add features to the configuration files. However, patches for bugs could sometimes be necessary. So, I'd feel more comfortable with linking to the version branch.

[christinaausley]

Will resolve merge conflicts in #3829 👍

resolved in discussion