Release 1.7.0: Compatibility docs

Update test matrix to latest 3 sets of k8s releases

Signed-off-by: Daniel Holbach <daniel@weave.works>

This update the test matrix to latest set of 3 minor k8s releases

Fixes: #347

Co-Authored-By: Jean-Philippe Evrard <open-source@a.spamming.party>

Bump github.com/prometheus/common from 0.24.0 to 0.25.0

Bump actions/stale from 3.0.18 to 3.0.19

Bumps [github.com/prometheus/common](https://github.com/prometheus/common) from 0.24.0 to 0.25.0.
- [Release notes](https://github.com/prometheus/common/releases)
- [Commits](https://github.com/prometheus/common/compare/v0.24.0...v0.25.0

)

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [actions/stale](https://github.com/actions/stale) from 3.0.18 to 3.0.19.
- [Release notes](https://github.com/actions/stale/releases)
- [Commits](https://github.com/actions/stale/compare/v3.0.18...v3.0.19

)

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: Daniel Holbach <daniel@weave.works>

Bump github.com/prometheus/common from 0.23.0 to 0.24.0

Bumps [github.com/prometheus/common](https://github.com/prometheus/common) from 0.23.0 to 0.24.0.
- [Release notes](https://github.com/prometheus/common/releases)
- [Commits](https://github.com/prometheus/common/compare/v0.23.0...v0.24.0

)

Signed-off-by: dependabot[bot] <support@github.com>

Without this, we get multiple questions about our testing.
This should help clarify the tests and our coverage by:
- Simplifying our coverage
- Documenting better the purpose of each workflow file
- Documenting our testing and development activities better.

Bump github.com/prometheus/common from 0.18.0 to 0.23.0

docu: update url for ms teams notifications, fixes #362

Bumps [github.com/prometheus/common](https://github.com/prometheus/common) from 0.18.0 to 0.23.0.
- [Release notes](https://github.com/prometheus/common/releases)
- [Commits](https://github.com/prometheus/common/compare/v0.18.0...v0.23.0

)

Signed-off-by: dependabot[bot] <support@github.com>

Use stable kind-action

We are relying on master, which might break anytime (or in this
case, moved to another branch).

Instead we should rely on a stable version, and unfreeze if
necessary. Dependabot helps us maintain those releases anyway.

Add parameter for delaying release of lock

Merge pull request #324 from weaveworks/dependabot/go_modules/github.com/prometheus/client_golang-1.10.0

Bump github.com/prometheus/client_golang from 1.8.0 to 1.10.0

Bumps [github.com/prometheus/client_golang](https://github.com/prometheus/client_golang) from 1.8.0 to 1.10.0.
- [Release notes](https://github.com/prometheus/client_golang/releases)
- [Changelog](https://github.com/prometheus/client_golang/blob/master/CHANGELOG.md)
- [Commits](https://github.com/prometheus/client_golang/compare/v1.8.0...v1.10.0

)

Signed-off-by: dependabot[bot] <support@github.com>

Bump github.com/containrrr/shoutrrr from 0.4.3 to 0.4.4

Bumps [github.com/containrrr/shoutrrr](https://github.com/containrrr/shoutrrr) from 0.4.3 to 0.4.4.
- [Release notes](https://github.com/containrrr/shoutrrr/releases)
- [Changelog](https://github.com/containrrr/shoutrrr/blob/main/goreleaser.yml)
- [Commits](https://github.com/containrrr/shoutrrr/compare/v0.4.3...v0.4.4

)

Signed-off-by: dependabot[bot] <support@github.com>

Bump github.com/containrrr/shoutrrr from 0.4.2 to 0.4.3

Bumps [github.com/containrrr/shoutrrr](https://github.com/containrrr/shoutrrr) from 0.4.2 to 0.4.3.
- [Release notes](https://github.com/containrrr/shoutrrr/releases)
- [Changelog](https://github.com/containrrr/shoutrrr/blob/main/goreleaser.yml)
- [Commits](https://github.com/containrrr/shoutrrr/compare/v0.4.2...v0.4.3

)

Signed-off-by: dependabot[bot] <support@github.com>

Without this patch, it's not clear that we added command line
arguments recently. This should expose our latest changes in the
future released manifest.

Add prometheus export metrics functional testing

Reduce false positives

Without this change, the "Test helm chart (install) action" will
rightfully succeed when our helm chart gets installed and has
no syntax issues. However, it doesn't test if kured is properly
installed. For example, the helm chart can try to install a
yet unpublished image, and our test will succeed, as the syntax
is still valid.

This is a problem, as everything looks green, but it's not
effectively working. Our other jobs are focusing on code changes,
so they rightfully override the image tag, which is not what
we want in this "Test helm chart" action.

This fixes it by adding an extra job in the workflow, depending
on the chart testing.

Add force-reboot after force-timeout duration has been exceeded

Without this, we can't know if the exposed prometheus metrics
behave properly.

This is a problem, as the only way we can evaluate the success
(right now), is a compilation success or failure from kured.
While this is a good start, it doesn't translate to what we
claim to offer: A boolean showing if a reboot is required.

This fixes it by creating a new github action workflow testing
if the float64 gauge is properly showing 0 for no reboot, 1 for reboot.
This is done by exposing the metrics endpoint through a node port.
A helm chart change was required to have the ability to expose
the service on a node port. We connect to the kind node through
docker in the `tests/test-metrics.sh`, where we curl the nodeport,
extract the only relevant metric, and compare it to the expected result.

This support throtteling of reboots across the cluster
and allows rebooted nodes to reschedule pods, e.g.
to synchronize replicated state before rebooting the next node.

chore: retry daemonset get operations

update to latest k8s deps of 1.20 branch

Signed-off-by: Daniel Holbach <daniel@weave.works>