Upgrade mkdocs and mkdocs-material

[trickeydan]

Upgrades mkdocs and other dependencies, notably upgrading mkdocs-material to v7.

Also updated mkdocs.yml for slight changes in config. Some icons are slightly different due to the old icon-set no longer being available.

Help Requested: I am unable to work out why the menu structure doesn't render as intended.

Preview when rendered: https://static.trickey.io/runbook/

(I ended up on this adventure when attempting to do #2 as a quick thing)

[RealOrangeOne]

I am unable to work out why the menu structure doesn't render as intended.

I remember diving into this a while back. I don't believe it is possible anymore. It appears it broke around the time the navigation was rewritten in mkdocs-material (6.2.0).

After digging around this again, I've submitted an issue upstream: squidfunk/mkdocs-material#3076

[RealOrangeOne]

Suggestion: We should add the navigation.index feature. It means the dropdowns are clickable and have navigation, which will be incredibly helpful for some of the content we write.

[PeterJCLaw]

Agree, though perhaps not as part of this upgrade PR?

[PeterJCLaw]

Aside: I don't think your repro needs navigation.instant

[PeterJCLaw]

(I was digging into the nav issues too, but @RealOrangeOne beat me to an answer)

[PeterJCLaw]

nit: does the ordering & quoting of these matter? (Wondering whether the diff can be reduced by keeping the previous ordering & removing the quotes.)

[PeterJCLaw]

nit: Is this a required part of the upgrade?

[PeterJCLaw]

Agree, though perhaps not as part of this upgrade PR?

[RealOrangeOne]

From the related issue, it's no longer possible to have pages like we currently have them.

Personally I'd suggest we have a small meta section about the runbook itself which houses these page, or we attempt to bake them into he homepage page itself (that'll get quite long).

[PeterJCLaw]

A breaking change removing something that is actually kinda hard to achieve another way occurring in a non-major release and then relegated to a footnote is rather disappointing IMO.

As I understand it the alternatives are:

• move the content to a meta folder and accept that it won't show up on the root page (plus maybe find some way to hide that folder from the tabs)
• some kind of redirect so that there is no actual root page and instead the root is /meta (would need to separately work out how to ensure that the meta directory's entry is the first tab in the list)
• fork the theme and/or override some aspect of it
• a plugin to adjust the nav (is that possible?)
• fully specify the entire nav tree in the config