Bevan Arps

We still want to do something to reduce the workload of the generator.

Sufficiently addressed by #3803

Goal is to allow people to compose a new pipeline for a new situation with some assurity that the result will work.

Bringing into **v2.2.0** as this is about smoothing the experience for users.

> I did some testing around the properties mentioned above ... Given the [above comment](https://github.com/Azure/azure-service-operator/issues/1415#issuecomment-824339179) by @matthchr, I believe the standard properties are not sufficient for the ASO use case....

Another quirk - you can only specify `createMode: recover` if there is an existing vault to recover - so it's very much NOT a goal state design.

Closing out as we no longer do a spec hash; see #2811 for follow up.

This is no longer happening regularly; once #2875 has been completed (which should just about eliminate timeouts) we can close this.

Retaining for now. @theunrepentantgeek to investigate whether we need these.

No longer required; we've decreased the number of suppressions organically and most of the remaining ones make sense.