Update `dsc resource list` output schema to include `methods` about dsc

[SteveL-MSFT]

The source of truth for that information is from the manifest which is nested in the resource json/yaml. The table view is a convenience, but I can see it has a similar problem we have in PowerShell which is a column header may not be a property on the object. We could do the same as in PS7 and italicize Methods and doc it rather than adding a property that just pulls the info from somewhere else that is already on the object.

[michaeltlombardi]

The source of truth for that information is from the manifest which is nested in the resource json/yaml.

That's also true for the version, type name, and description, I think. My understanding is that moving those keys to the top level of the return object is to make it easier for users/integrating tools to process and surface the information.

The other consideration is for adapted resources, like from PSDSC - in that specific case, the resources all (currently) implement the same methods, but in the future they may support export or use synthetic testing instead of implementing the test method. Right now, adapter resources aren't required to return manifests for the adapted resources from their list command.

[SteveL-MSFT]

This is addressed calling them caps for capabilities