I'm not sure where that comment came from: I looked in the tor-nagios
history and couldn't find a trace of that plugin.

We might set it up eventually though, as part of team#40706.

This will look simpler, especially if we're stuck typing this by
hand.

In general, I stopped using `-k all` blindly everywhere: the default
is to update the latest kernel, which is usually the right thing.

I did not run these commands on chi-node-10, and the login console works
fine via both the iDRAC and the java console.

These settings were tested to work on the PowerEdge R610 servers. Also
this moves the instructions under "Serial console access" section
instead of "Other BIOS config".

This moves goals, approvals, alternatives, and costs to the policy
template. It seems we often forgot about those items when writing
policy and would end up filling them up only when writing the service
docs, which is too late for many of those.

We keep a cross-reference to the policy in the service docs though.

This makes it so it has a chance of upgrading config files that might
have changed after bullseye. It will not necessarily remove the
conflict files, but will make the cleanup certainly easier.

In fact, we could also fix clean_conflicts to automatically resolve
those as well.

mostly to make a real link for the policy, wrap paragraphs so they are
more readable in plain text, and make a bullet list for the
revocation policy, and clarify each part is a "or"

This was copied verbatim from:

https://gitlab.torproject.org/tpo/community/team/-/wikis/Tor-Project-BBB-Account-Policy

That page will be replaced by a link to this section.

We were using both before, which was confusing, and were not
explaining where the `example-01` was coming from. We also clarify
that the documentation in this case doesn't cover the general case, as
tb-build-03 was not setup in the best way...

/cc @lavamind