Requesting ability to capture all resources, even those which aren't fully understood by AzureHound

AzureHound doesn't support every sort of resource that can exist on Azure, obviously this is a necessary compromise due to the sheer number of resource types. However, even for those resources which don't have explicit support, it would be great if they could still be captured by AzureHound and stored as nodes, so they can be used as targets.

For example, if I have an Azure Database which is considered a high value target, there is no way to evaluate its security using AzureHound, as it does not yet support Azure Databases. If there were an option to capture it as an "unknown" resource, it could still at least be set as a target, and I can see who can get ownership of it.

The issue names no files, tests, or entry points, so first map AzureHound's Azure resource collection and node-modeling paths. Define how unsupported resources become identifiable unknown nodes, then verify that they can be stored, selected as targets, and used to inspect ownership relationships.