Upcoming Deprecation of Jira Cloud Search APIs

[glewandowski]

Is your feature request related to a problem? Please describe.
On October 31, 2024, Atlassian announced the deprecation of four Jira Cloud search APIs. These APIs will be replaced with new, more efficient alternatives through our enhanced JQL service, which are currently available for use. You can read more about these new APIs here.
Effective May 1, 2025, Atlassian will remove the following Jira REST endpoints:

• GET /rest/api/3/search
• POST /rest/api/3/search
• POST /rest/api/3/search/id
• POST /rest/api/3/expression/eval
  We have identified that this library may be used to access the deprecated endpoints in Jira Cloud. Failing to migrate to the new APIs before May 1, 2025, could negatively impact any solutions that depend on this library. By evolving our JQL service, we aim to provide a more reliable, performant, and scalable Jira experience tailored to meet the needs of enterprise customers.
  If you have any questions or require further assistance, please do not hesitate to ask on our developer community forum

Describe the solution you'd like
There're at least 2 places that use deprecated API

go-atlassian/jira/internal/search_impl_adf.go

Line 71 in cc7e2ae

func (i *internalSearchADFImpl) Get(ctx context.Context, jql string, fields, expands []string, startAt, maxResults int, validate string) (*model.IssueSearchScheme, *model.ResponseScheme, error) {

go-atlassian/jira/internal/search_impl_rich_text.go

Line 94 in cc7e2ae

endpoint := fmt.Sprintf("rest/api/%v/search?%v", i.version, params.Encode())

To mantain compatibility with Jira Cloud, they need to updated.

• URL has changed to rest/api/{2|3|latest}/search/jql
• validate parameter is removed with no replacement
• startAt parameter is removed with nextPageToken replacement

Describe alternatives you've considered
N/A

Additional context
N/A