Update GH files for issue templates and Jira automation

This PR updates the .github files to
* Ensure we have a file for tasks/enhancements
* Ensure we expose dod in task issues
* Use the FastAPI for ticket sync, and not JIRA_URL

.github/.jira_sync_config.yaml

@@ -0,0 +1,31 @@
+settings:
+    # Jira project key to create the issue in
+  jira_project_key: "KF"
+
+  # Dictionary mapping GitHub issue status to Jira issue status
+  status_mapping:
+    opened: Untriaged
+    closed: done
+
+  # (Optional) GitHub labels. Only issues with one of those labels will be synchronized.
+  # If not specified, all issues will be synchronized
+  labels:
+    - bug
+    - enhancement
+
+  # (Optional) (Default: false) Add a new comment in GitHub with a link to Jira created issue
+  add_gh_comment: true
+
+  # (Optional) (Default: true) Synchronize issue description from GitHub to Jira
+  sync_description: true
+
+  # (Optional) (Default: true) Synchronize comments from GitHub to Jira
+  sync_comments: false
+
+  # (Optional) (Default: None) Parent Epic key to link the issue to
+  epic_key: "KF-4805"
+
+  # (Optional) Dictionary mapping GitHub issue labels to Jira issue types.
+  # If label on the issue is not in specified list, this issue will be created as a Bug
+  label_mapping:
+    enhancement: Story

.github/ISSUE_TEMPLATE/task.yaml

@@ -9,6 +9,14 @@ body:
         proposal! Before submitting your issue, please make sure there
         isn't already a prior issue concerning this. If there is,
         please join that discussion instead.
+  - type: textarea
+    id: enhancement-proposal-why
+    attributes:
+      label: Why it needs to get done
+      description: >
+        Describe why it needs to get done
+    validations:
+      required: true
   - type: textarea
     id: enhancement-proposal-what
     attributes:
@@ -18,10 +26,10 @@ body:
     validations:
       required: true
   - type: textarea
-    id: enhancement-proposal-why
+    id: enhancement-proposal-dod
     attributes:
-      label: Why it needs to get done
+      label: When is the task considered done
       description: >
-        Describe why it needs to get done
+        Describe what are the requirements for the task to be considered done
     validations:
       required: true