ResourceToken support

[ausfeldt]

Description

Add Users and Permissions to the SDK. Constructor overload(s) to CosmosClient that supports multiple permissions/resource tokens is not included in this PR.

Because there is not SelfLinks or UriFactory like v2, constructor overloads were added to PermissionProperties which creates the ResourceLink from constructed LinkUri.

The resource token is a string just like account key and can be used as an alternative. I would like change the variable name in the signature but it would be a breaking change because it would break those that use named parameters. Also I can't create a second overload as it would be the same signature. I updated the constructor parameter documentation. I could always introduce a constructor overload for IEnumerable which will cover any user scenario and be more explicit.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

//Database.cs
User GetUser(string id);

Task<UserResponse> CreateUserAsync(
	string id,
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));
	
Task<UserResponse> UpsertUserAsync(UserProperties userProperties, 
	RequestOptions requestOptions = null, 
	CancellationToken cancellationToken = default(CancellationToken));

FeedIterator<T> GetUserQueryIterator<T>(
	string queryText = null,
	string continuationToken = null,
	QueryRequestOptions requestOptions = null);

FeedIterator<T> GetUserQueryIterator<T>(
	QueryDefinition queryDefinition,
	string continuationToken = null,
	QueryRequestOptions requestOptions = null);
	
//User.cs
string Id { get; }

Task<UserResponse> ReadAsync(
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));
	
Task<UserResponse> ReplaceAsync(
	UserProperties userProperties,
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));
	
Task<UserResponse> DeleteAsync(
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));
	
Permission GetPermission(string id);

Task<PermissionResponse> CreatePermissionAsync(
	PermissionProperties permissionProperties,
	int? tokenExpiryInSeconds = null,
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));
			
Task<PermissionResponse> UpsertPermissionAsync(
	PermissionProperties permissionProperties,
	int? tokenExpiryInSeconds = null,
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));

FeedIterator<T> GetPermissionQueryIterator<T>(
	string queryText = null,
	string continuationToken = null,
	QueryRequestOptions requestOptions = null);

FeedIterator<T> GetPermissionQueryIterator<T>(
	QueryDefinition queryDefinition,
	string continuationToken = null,
	QueryRequestOptions requestOptions = null);
	
//Permission.cs
string Id { get; }

Task<PermissionResponse> ReadAsync(
	int? tokenExpiryInSeconds = null,
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));

Task<PermissionResponse> ReplaceAsync(
	PermissionProperties permissionProperties,
	int? tokenExpiryInSeconds = null,
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));
			
Task<PermissionResponse> DeleteAsync(
	RequestOptions requestOptions = null,
	CancellationToken cancellationToken = default(CancellationToken));
			

[kirankumarkolli]

CosmosClient authKey rename -> authKeyOrResourceToken

[kirankumarkolli]

Create a backlog item for Fluent versions of these API's

[j82w]

Would it be better to just use: this.ClientContext.ValidateResource(userProperties.Id);

[j82w]

How can user UT this?

[ausfeldt]

Make LinkUri public on Container, but I thought we don't want to do that.

[kirankumarkolli]

Please follow-up comments through issues.