Keep v2 support for search

[aditi-kantata]

Enable the support for v2 search as well, as for some clients using on-prem server for jira, v3 is not yet supported. The client can call jql_v2 and the gem would hit the v2 search api.

[ajitkantata]

LGTM

[b6b]

I like bringing back the old implementation 👍

@mavenlink/integrations-solutions The one thought I have is that this unfortunately just moves old behavior to a different method instead of keeping it fully compatible. It will be a bit of an annoyance changing things again, but what does everyone thing of preferring to keep this self.jql and updating the v3 search to be self.jql_v3?

[ananta0799]

LGTM

[aditi-kantata]

I like bringing back the old implementation 👍

@mavenlink/integrations-solutions The one thought I have is that this unfortunately just moves old behavior to a different method instead of keeping it fully compatible. It will be a bit of an annoyance changing things again, but what does everyone thing of preferring to keep this self.jql and updating the v3 search to be self.jql_v3?

Thats interesting, but why I kept the v3 as self.jql is because, going forward that will become the default and v2 could be mentioned explicitly holding only for a few calls.

[Theotata]

I like bringing back the old implementation 👍
@mavenlink/integrations-solutions The one thought I have is that this unfortunately just moves old behavior to a different method instead of keeping it fully compatible. It will be a bit of an annoyance changing things again, but what does everyone thing of preferring to keep this self.jql and updating the v3 search to be self.jql_v3?

Thats interesting, but why I kept the v3 as self.jql is because, going forward that will become the default and v2 could be mentioned explicitly holding only for a few calls.

I understand that v3 will be the default for search but reviewing the pattern on your other PR, I think self.jql_v3 makes it clearer that this is part of the phased migration to v3 rather than being part of the "baseline/majority" version. I'm kinda ok either way but slightly leaning on self.jql_v3
from PR