Remove the various client traits

[rylev]

This is the first in (I hope) many PRs to remove most of the traits we use internally in Cosmos.

This removes all traits which seek to require client getter methods. I don't see any advantage to these being a part of a trait instead of being on the struct itself. I believe the thought originally behind this was consistent naming, but I think it's easier to manually keep track of that rather than relying on traits (after all, the user could just choose to not implement the trait at all).

I believe we should remove all traits which exist only to enforce naming conventions. I believe this will most likely result in removing the entire traits.rs file in Cosmos DB.

[MindFlavor]

I like it even though it removes the documentation property of the traits for the sake of some typing. For example by enumerating the implementers of TriggerClientRequired one can find all the functions pertaining to triggers.

It's probably best to keep the code simpler 👍 !

[rylev]

even though it removes the documentation property of the traits for the sake of some typing.

I'm not so sure I see that as being a very common need. When will people want to see all the types that implement that method?

The most important change that this leads to is it improves documentation. Below is a screenshot of the docs. Notice that it's easy to see the permission_client method in the docs now. The methods defined on the traits are only viewable with the docs expanded and even they they are surrounded by the noise of the trait definitions.