Fix ancestry_path for top-level resources

[nstogner]

Currently asset.ancestry_path assumes the resource lives within a project. This does not work for folders, etc.

[nstogner]

Examples ancestry_path for top-level resources:

organization: organization/{org_id}
folder: organzation/{org_id}/folder/{folder}
project: organzation/{org_id}/folder/{folder}/project/{project}

[nstogner]

Strategy: Move the calculation ancestry_path upstream into the conversions library. See GoogleCloudPlatform/magic-modules#1620.

[nstogner]

PS: Once 1620 (above) gets merged, we should be able to get rid of the internally defined Asset struct and use the one from the conversions library.

[melinath]

Closing - seems to be a duplicate of #5.

[morgante]

@melinath Last I checked, I think we still need a fix for this. In particular, if you are validating a google_folder resource it should return an ancestry_path of organzation/{org_id}/folder/{parent_folder}.

[melinath]

Whereas now I assume it includes the project as well? I was thinking of this as being a duplicate of #5 (and by extension of #206) but we could probably resolve it separately in the shorter term.

[morgante]

Right, I think now we use a nonsense project in the ancestry path (folders can't have projects as their parent).

This might be a dupe of #5, but since you closed both I think there was more detail here.