Extend VBase clients with conflict handler endpoints

[vitorflg]

What is the purpose of this pull request?

• Extend the VBase client to have more options to handle conflicts

What problem is this solving?

Slack thread

How should this be manually tested?

• You can test it yarn linking all dependencies(@vtex/api, this module, and the cli-plugin-workspace), and running with the alias:
  vtex-test promote After that, listing to conflicts should return an empty array.

Screenshots or example usage

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires change to documentation, which has been updated accordingly.

[filafb]

The changed required here is just the target branch, which should be main, not 2.x.

This VBase client is very specific for managing buckets and files for pages-graphql. In the new content structure, will this client still be needed or changed in any way?

[vitorflg]

The changed required here is just the target branch, which should be main, not 2.x.

This VBase client is very specific for managing buckets and files for pages-graphql. In the new content structure, will this client still be needed or changed in any way?

It will be needed and we won't have to change it! I created another PR with main as base: #1236