add Context counterparts methods for Client

[dungdm93]

Merge after #163

[dungdm93]

cc @chris-ruecker, @anmoel

[anmoel]

why do you move the creation of ctx.background from net.http package into our client? what is the benefit?

[dungdm93]

@anmoel Because it's shorter than duplicate code with CreateContext like this:

func (s *RepositoryService[R]) Create(ctx context.Context, repo R) error {
	data, err := tools.JsonMarshalInterfaceToIOReader(repo)
	if err != nil {
		return err
	}
	body, resp, err := s.client.Post(s.endpoint, data)
	if err != nil {
		return err
	}
	if resp.StatusCode != http.StatusOK && resp.StatusCode != http.StatusCreated {
		return fmt.Errorf("could not create repository %v: HTTP: %d, %s", repo, resp.StatusCode, string(body))
	}
	return nil
}

[anmoel]

i mean, why you want to manage the context? in our old code, we don't manage the context. we used the http client functions without context.

[dungdm93]

To support request cancellation, timeout and so on.

An example use-case is terraform-provider-nexus: All Resource.Create|Delete|Exists|Read|Update methods are deprecated in favor of XContext counterparts

// Deprecated: Use CreateContext or CreateWithoutTimeout instead. This
// implementation does not support request cancellation initiated by
// Terraform, such as a system or practitioner sending SIGINT (Ctrl-c).
// This implementation also does not support warning diagnostics.
Create [CreateFunc](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema@v2.36.1#CreateFunc)