Fix Acceptance Criteria section (#1371)

* Change required fields and markdown for screenshots

- Screenshot field is now Markdown
- Required fields changed
- Make break lines consistent in issue forms

* Markdown for Acceptance Criteria

Transform to Markdown the Acceptance Criteria

* Fix Acceptance Criteria

---------

Co-authored-by: Jean-Robin <jeanrobin.medori@avaiga.com>

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -116,20 +116,10 @@ body:
     validations:
       required: false
 
-  - type: checkboxes
-    id: acceptance_criteria
-    attributes:
-      label: Acceptance Criteria
-      options:
-        - label: "Ensure new code is unit tested, and check code coverage is at least 90%."
-          required: false
-        - label: "Create a related issue in taipy-doc for documentation and Release Notes if relevant."
-          required: false
-
   - type: markdown
     attributes:
       value: |
-        ## Acceptance Criteria
+        ### Acceptance Criteria
         
         - [ ] Ensure new code is unit tested, and check code coverage is at least 90%.
         - [ ] Create related issue in taipy-doc for documentation and Release Notes.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -44,7 +44,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        ## Acceptance Criteria
+        ### Acceptance Criteria
         
         - [ ] Ensure new code is unit tested, and check code coverage is at least 90%.
         - [ ] Create related issue in taipy-doc for documentation and Release Notes.

.github/ISSUE_TEMPLATE/refactor-code.yml

@@ -19,7 +19,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        ## Acceptance Criteria
+        ### Acceptance Criteria
         
         - [ ] Ensure new code is unit tested, and check code coverage is at least 90%.
         - [ ] Propagate any change on the demos and run all of them to ensure there is no breaking change.