Description

For ease these were initially added to resources which is is more used for an "abstract" resource i.e. other resources probably inherit/use this.

MeshIdentity/MeshTrusts ideally don't belong in here and should be in their own module or modules, either:

• mesh-identities and mesh-trusts; or
• mtls containing both potentially subfolder'd into mtls/meshidentities, mtls/meshidentities

I kinda like having an mtls module containing all mtls stuff which can be enabled disabled in one shot. But we currently have a pattern of one module per resource and then we sometimes wrap those into a parent module (as is the case with service-mesh.

All in all, I guess we should stick with the "one module per resource" pattern for now at least