docs: add instructions to build a location path

[ricardolsmendes]

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass - N/A
• Code coverage does not decrease (if any source code was changed) - N/A
• Appropriate docs were updated (if necessary)

Fixes #68 🦕

[tswast]

Looks like these helpers were added back in https://github.com/googleapis/python-datacatalog/pull/64/files#diff-88240775a7bf30997273f4cd159e38bbff4ef74a98e065ec045706d3acf5f125R287

(To be released in 3.0 #71)

[ricardolsmendes]

Looks like these helpers were added back in https://github.com/googleapis/python-datacatalog/pull/64/files#diff-88240775a7bf30997273f4cd159e38bbff4ef74a98e065ec045706d3acf5f125R287

(To be released in 3.0 #71)

Thanks for letting me know, @tswast!

[ricardolsmendes]

Hey @tswast, I've tested v3.0.0 and the helper methods are back but with slightly different names, prefixed with common_: common_billing_account_path, common_folder_path, common_location_path, common_organization_path, and common_project_path.

Maybe it's worth keeping this change to the v2.0,0 migration guide and write new instructions to the v3.0.0. WDYT? 🤔

[tswast]

Since 2.0 hasn't been out all that long, maybe we should update the guide to be from 1.0 to 3.0?

[ricardolsmendes]

Since 2.0 hasn't been out all that long, maybe we should update the guide to be from 1.0 to 3.0?

Makes sense. I can work on this in a couple of days if it works for you.

[ricardolsmendes]

Closing this PR because I'm updating the upgrade guide to be from 1.0 to 3.0 in #77...