Is your feature request related to a problem? Please describe.

I am developing a project dependent on the go-jira and I would like to start by using v3 Jira APIs (https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/)

Currently, (almost) all API calls are based on the v2 Jira API version. I can (and have) use the NewRequest/Do pattern described in the examples, however this is kludgy. I would prefer to use direct methods to obtain the results in the same manner that v2 API is currently supported. Also, since the v3 structures are not supported then I would be required to re-implement the structures in my project.

Describe the solution you'd like

I would like to have built-in support for v3 APIs. Preferably so that both v2 and v3 are supported by the same version of the library.

Describe alternatives you've considered

As mentioned in the description I can request the v3 APIs directly through NewRequest/Do and write my own deserializer for the changed structures but this is suboptimal as I am probably duplicating work that others require as well :)

Additional context

Looking at the OpenAPI specification of the v3 APIs there are not that many changes, although that may depend on your point of view. For the most part, the v2 and v3 just have different endpoints (replacing 2 with 3, surprisingly :) ), but otherwise they return almost the same structures.

The major difference is the ADF (Atlassian Document Format) which impacts how some fields are constructed. Instead of strings some APIs return values describing documents in specific JSON format. Please see the above link to the v3 API for the details. Additionally, note that while testing I have also seen some differences with parameters' support between the v2 and v3 APIs (specifically, the difference between project and project/search) but, while sometimes confusing, this can be addressed by samples and documentation.