ci(dependabot-pip): bump jira from 3.6.0 to 3.8.0 (RDT-922)

[dependabot]

Bumps jira from 3.6.0 to 3.8.0.

Release notes

Sourced from jira's releases.

v3.8.0

Minor Changes

• Add goal field to update/create sprint (#1806) @​zbarahal

Bugfixes

• add backward compatibility for createmeta_issuetypes & createmeta_fieldtypes (#1838) @​paminov

v3.7.0

[!NOTE]
Not released on PyPI (see 3.8.0)

What's Changed

• add Release Process doc by @​adehad in pycontribs/jira#1793
• Improve handling of Jira's retry-after handling by @​matthias-bach-by in pycontribs/jira#1825
• ISSUE-1836: Add Dashboard Support by @​jpavlav in pycontribs/jira#1837
• Update createmeta warning with new method names by @​mesozoic in pycontribs/jira#1820

New Contributors

• @​matthias-bach-by made their first contribution in pycontribs/jira#1825
• @​jpavlav made their first contribution in pycontribs/jira#1837
• @​mesozoic made their first contribution in pycontribs/jira#1820

Full Changelog: pycontribs/jira@3.6.0...3.7.0

Commits

• fbdb2bf Add goal field to update/create sprint (#1806)
• 4960d8f add backward compatibility for createmeta_issuetypes & createmeta_fieldtypes ...
• e8104ea Update createmeta warning with new method names (#1820)
• fbcabe1 Add Dashboard Support (#1836, #1837)
• 4999a76 Improve handling of Jira's retry-after handling (#1825)
• ff6985b Bump beautifulsoup4 from 4.12.2 to 4.12.3 (#1808)
• ad17dc0 Bump sphinxcontrib-devhelp from 1.0.2 to 1.0.6 (#1811)
• a9793e0 Bump jinja2 from 3.1.2 to 3.1.3 (#1815)
• 90da800 Bump sphinxcontrib-serializinghtml from 1.1.9 to 1.1.10 (#1816)
• 0975053 More RTD maintenance (#1733)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

	Warnings
⚠️	The source branch "dependabot/pip/jira-3.8.0" incorrect format: contains more than one slash (/). This can cause troubles with git sync. Please rename your branch.

👋 Hello dependabot[bot], we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 7cd0138

[github-actions]

This PR is stale because it has been open 30 days with no activity. Remove Status: Stale label or comment or this will be closed in 7 days.

[github-actions]

This PR was closed because it has been stalled for 10 days with no activity.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.