refactor(api)!: show uid instead of parent_lookup DEV-1049

[RuthTurk]

🗒️ Checklist

1. run linter locally
2. update developer docs (API, README, inline, etc.), if any
3. for user-facing doc changes create a Zulip thread at #Support Docs Updates, if any
4. draft PR with a title <type>(<scope>)<!>: <title> DEV-1234
5. assign yourself, tag PR: at least Front end and/or Back end or workflow
6. fill in the template below and delete template comments
7. review thyself: read the diff and repro the preview as written
8. open PR & confirm that CI passes & request reviewers, if needed
9. delete this section before merging

📣 Summary

Update the drf-spectacular api documentation to use a consistent uid_<object_name> naming convention.

👀 Preview steps

1. ℹ️ checkout api/v2/docs
2. 🟢 [on PR] make sure that all parent_lookup_ have been changed to uid_ and that all nested uids are correct.
   Example:
   /api/v2/assets/{parent_lookup_asset}/hooks/{parent_lookup_hook}/logs/{uid}/
   Should be
   /api/v2/assets/{uid_asset}/hooks/{uid_hook}/logs/{uid_log}/
3. Test the endpoints to make sure they are still working

[noliveleger]

You may need to update the mapping in here

kpi/kpi/utils/schema_extensions/url_builder.py

Line 30 in 9f4a394

urls_pattern_mapping = {

[noliveleger]

First of all, congrats to have tackling this. It was indeed more complex than expected.

I found few tiny mistakes though 😇

• /api/v2/project-ownership/invites/{uid_invite_uid}/transfers/{uid_transfer}/
uid_invite_uid should be only uid_invite
• /api/v2/assets/{uid_asset}/data/{uid_data}/attachments/ . The documentation (inside the markdown) still refers to parent_lookup_data.
• /api/v2/assets/{uid_asset}/paired-data/{paired_data_uid}/ . For consistency, It would also change paired_data_uid to uid_paired_data
• /api/v2/organizations/{organization_id}/invites/, some other endpoints for organizations are using {id}. Let's use uid_organization everywhere if we can.