[Docs] configure issue form

[sdiazlor]

Description

Just saw this in Notion and took the opportunity to do so when reviewing the docs.

Closes #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (change restructuring the codebase without changing functionality)
• Improvement (change adding some improvement to an existing functionality)
• Documentation update

How Has This Been Tested

Checklist

• I added relevant documentation
• I followed the style guidelines of this project
• I did a self-review of my code
• I made corresponding changes to the documentation
• I confirm My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

[davidberenstein1957]

@sdiazlor do you have some example screenshots? also tagging @damianpumar and @leireropl @jfcalvo @frascuchon because they will be mostly working with this. Good example shown here: https://github.com/gradio-app/gradio/issues/new?assignees=&labels=bug&projects=&template=bug_report_template.yml

[davidberenstein1957]

@sdiazlor Did you see other modalities like markdown/dropdowns too? https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms

[sdiazlor]

These are the form previews. @damianpumar @leiyre @jfcalvo @frascuchon let me know if they would provide you the needed information or if you need more/less/other relevant request.

@davidberenstein1957 Yes, I checked the issue syntax, but I felt it would be better to use the textareas for the questions we have.

[github-actions[bot]]

Docs for this PR have been deployed hidden from versioning: https://docs.argilla.io/docs_configure-issue-form