Add new createmeta functions to comply with Jira 9 API

[Ry-DS]

This PR closes #1030

Adds new functions to maintain the same level of functionality, while also adding a deprecation warning for the old function.

To learn more about why this is needed, check out https://confluence.atlassian.com/jiracore/createmeta-rest-endpoint-to-be-removed-975040986.html

TODO:

• May be best to use the self.resource_url function for consistency's sake

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 33.33333% with 6 lines in your changes missing coverage. Please review.

Project coverage is 36.17%. Comparing base (272c7b2) to head (84d5bc5).
Report is 309 commits behind head on master.

Files with missing lines	Patch %	Lines
atlassian/jira.py	33.33%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1031      +/-   ##
==========================================
+ Coverage   35.97%   36.17%   +0.20%     
==========================================
  Files          35       39       +4     
  Lines        6783     6910     +127     
  Branches     1058     1073      +15     
==========================================
+ Hits         2440     2500      +60     
- Misses       4237     4303      +66     
- Partials      106      107       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gonchik]

does that dependency typing is built-in ?

[Ry-DS]

Typing is built into python 3, shouldn't be an issue if it's included.

[gonchik]

But we have still python2 clients ;(

[Ry-DS]

you should add python2 to the ci, as right now it only contains python 3. Rolled back the typing changes here: e8babc0 👍

[gonchik]

Main idea is remove python2 support, but time to time I receive emails ;)
That's why I have mentioned ;)

[pmilosev]

@Ry-DS please see my comment here: pycontribs/jira#1527 (comment)

It looks like cloud Jira and Jira DC/Server have independent REST API and any client connecting to it should account for potential differences. Cloud JIRA still uses the createmeta endpoint and does not support the new API.
This probably doesn't affect your change here as you only added functions that use the new endpoints, but you might want to check your deprecation warning and eventually guard it with some if statements as the createmeta endpoint is not deprecated in general.

(you don't need to act on this, but since I used your PR as reference on how to implement the support in pycontrib/jira I thought sharing this info)

[gonchik]

@pmilosev thanks for that mention.
I see interesting conditions related to the version checkers.