Source Jira: Removed Connector Domain Pattern from Spec

[sumegim]

What

The pattern for the JIRA domain will not necessarily end in atlassian.net. (e.g. cloud hosted JIRA can also be jira.com and on premise installations can also deviate from this pattern).

I propose removing this restriction. Our opinion is that it's too strict and brings little to no value.

This PR fixes: #7502
Closes #11414

How

Removed pattern requirement from domain filed in the JIRA connector

🚨 User Impact 🚨

no breaking changes

Pre-merge Checklist

Expand the relevant checklist and delete the others.

Updating a connector

Community member or Airbyter

• Grant edit access to maintainers (instructions)

• Secrets in the connector's spec are annotated with airbyte_secret

• Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.

• Code reviews completed

• Connector version has been incremented

  • Version has been bumped according to our Semantic Versioning for Connectors guidelines
  • Dockerfile has updated version

• Documentation updated

  • Connector's README.md
  • Connector's bootstrap.md. See description and examples
  • Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example

• PR name follows PR naming conventions

[CLAassistant]

All committers have signed the CLA.

[willi-mueller]

I'd love to see this on master!

[marcosmarxm]

Thanks @sumegim

[marcosmarxm]

/test connector=connectors/source-jira

🕑 connectors/source-jira https://github.com/airbytehq/airbyte/actions/runs/4659948172
✅ connectors/source-jira https://github.com/airbytehq/airbyte/actions/runs/4659948172
Python tests coverage:

Name                      Stmts   Miss  Cover
---------------------------------------------
source_jira/utils.py         21      0   100%
source_jira/__init__.py       2      0   100%
source_jira/source.py        47      4    91%
source_jira/streams.py      640     63    90%
---------------------------------------------
TOTAL                       710     67    91%

Build Passed

Test summary info:

=========================== short test summary info ============================
SKIPPED [1] ../usr/local/lib/python3.9/site-packages/connector_acceptance_test/tests/test_core.py:578: The previous and actual discovered catalogs are identical.
================== 39 passed, 1 skipped in 725.27s (0:12:05) ===================

[marcosmarxm]

/publish connector=connectors/source-jira

🕑 Publishing the following connectors:
connectors/source-jira
https://github.com/airbytehq/airbyte/actions/runs/4660152343

Connector	Did it publish?	Were definitions generated?
connectors/source-jira	✅	✅

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️