feat: return object id on object operations

[fenos]

What kind of change does this PR introduce?

feature

What is the current behavior?

currently is not possible to create relationships from the client side to an object because the id is never returned

What is the new behavior?

object id is returned on the following operations:

• createObject
• copyObject
• updateObject

[coveralls]

Pull Request Test Coverage Report for Build 3159680588

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 29 of 29 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 85.818%

---

Totals
Change from base Build 3157262546:	0.02%
Covered Lines:	2906
Relevant Lines:	3340

---

💛 - Coveralls

[inian]

Let's change it to id. Key is the only place we use capital case - we should change that to key in the next breaking release

[groud]

Hello!

We are using supabase on our project and we would need the ID returned somehow, or at least a way to get it using an API endpoint. I've just found this PR would likely solve our issue and I was wondering if it was planned to merge it (once rebased), or if another solution is planned to be provided soon ?

[fenos]

This is now been implemented by #332