Fix bookmarks creation endpoint

[adriansmares]

Summary

References #6483

In short, /users/bookmarks can be interpreted as a request towards the user called bookmarks. The only reason why this doesn't happen is that methods don't overlap - bookmark creation uses POST while user updates require PUT.

The API itself is very hierarchical - sub-entities generally contain the top level entity ID in the path in order to avoid these possible path overlaps, and this should apply here as well.

Changes

• Ensure that UserRegistry HTTP paths do not overlap with UserBookmarkRegistry HTTP paths.

Testing

N/A. This just changes the generated code. No testing required.

Regressions

N/A. The Console does not depend on this feature, and the CLI clients are unaffected as they use gRPC.
It may be tempting to say that this API has already been released and is frozen, but there are no real clients for it, so it's better to fix this now than later.

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Testing: The steps/process to test this feature are clearly explained including testing for regressions.
• Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

[nicholaspcr]

Good catch.