A nicer way of handling distro specific docs

[SludgeGirl]

Currently if a downstream has their own documentation for the various Cockpit modules, this can only be changed and update by maintaining a patch to handle this downstream

I think it'd be a good and pretty intrusive feature to check /etc/os-release for ID and ID_LIKE and see if any of those are present in the manifest docs-OS_ID so this would end up looking something like:

{
    "docs": [
        {
            "label": "Web Console",
            "url": "https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/managing_systems_using_the_rhel_9_web_console/index"
        }
    ],
    "docs-opensuse": [
        {
            "label": "Web Console",
            "url": "link"
        }
    ],
}

Defaulting back to whatever might be matched and failing all of that, back to the stock Cockpit documentation

It should only require a small amount of logic changes here:
https://github.com/cockpit-project/cockpit/blob/main/pkg/shell/topnav.tsx#L127-L130

We're good to handle the development of this, I just wanted to open a discussion about this first

[jelly]

@martinpitt and I recently discussed that we show RHEL 9 documentation on RHEL 10 and we possibly want to detect and conventionalize this.

[Venefilyn]

My first thought was that we should just modify this with a script during build time