Adiciona templates para Relatório de Bug e Solicitação de Recursos

- Cria um template para Relatório de Bug com os seguintes campos:
  - Termos de aceite
  - Descrição detalhada do problema
  - Expectativa versus observação
  - Capturas de tela/vídeos
  - Versão da API
  - Ambiente
  - Especificações adicionais do ambiente
  - Logs (se aplicável)
  - Notas adicionais

- Cria um template para Solicitação de Recursos com os seguintes campos:
  - Termos de aceite
  - Tipo de recurso
  - Motivação para a solicitação
  - Exemplos de uso
  - Ideias de desenvolvimento
  - Notas adicionais

Author: jrCleber

.github/ISSUE_TEMPLATE/-en--bug-report.md

@@ -0,0 +1,106 @@
+name: Bug Report
+description: Create a report to help us improve.
+labels:
+  - bug
+  # - help wanted
+# Automatically assign the issue to:
+# assignees: DavidsonGomes
+body:
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Welcome!
+      description: |
+        The issue tracker is only for reporting bugs and feature requests.
+        For user-related support questions, please visit:
+          - [Discord](https://evolution-api.com/discord)
+          - [WhatsApp Group](https://evolution-api.com/whatsapp)
+          <br/>
+
+        **DO NOT OPEN AN ISSUE FOR GENERAL SUPPORT QUESTIONS.**
+
+      options:
+        - label: Yes, I have searched for similar issues on [GitHub](https://github.com/EvolutionAPI/evolution-api/issues) and found none.
+          required: true
+
+  - type: textarea
+    attributes:
+      label: What did you do?
+      description: |
+        How to write a good bug report?
+
+        - Respect the issue template as much as possible.
+        - The title should be short and descriptive.
+        - Explain the conditions that led you to report this issue: the context.
+        - The context should lead to something, an idea or problem you are facing.
+        - Be clear and concise.
+        - Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown)
+      placeholder: Describe the problem you encountered in detail.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What did you expect?
+      placeholder: Describe what you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What did you observe instead of what you expected?
+      placeholder: Explain what actually happens when you follow the steps above.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Screenshots/Videos
+      placeholder: |
+        If possible, add screenshots or videos that illustrate the problem. This can be extremely helpful in understanding the issue better.
+
+  - type: textarea
+    attributes:
+      label: Which version of the API are you using?
+      description: |
+        Enter the version number found in the `version` property of the **package.json**.
+      placeholder: Paste the version here.
+    validations:
+      required: true
+
+  - type: dropdown
+    id: select
+    attributes:
+      label: What is your environment?
+      options:
+        - Windows
+        - Linux
+        - Mac
+        - Docker
+        - Other
+    validations:
+      required: true
+  
+  - type: textarea
+    attributes:
+      label: Other environment specifications
+      placeholder: 'Hardware/Software: [e.g., CPU, GPU]'
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: If applicable, paste the log output
+      description: |
+        Please attach any logs that might be related to the issue.
+        If the logs contain sensitive information, consider sending them privately to one of the project maintainers.
+      placeholder: Paste the application log here.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Additional Notes
+      description: Include any other information you think might be useful to understand or resolve the bug.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/-en--bug-report.yaml

@@ -0,0 +1,85 @@
+name: Feature Request
+description: Suggest ideas for the project.
+labels:
+  - enhancement
+# Automatically assign the issue to:
+# assignees: DavidsonGomes
+body:
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Welcome!
+      description: '**DO NOT OPEN FOR GENERAL SUPPORT QUESTIONS.**'
+
+      options:
+        - label: Yes, I have searched for similar requests on [GitHub](https://github.com/code-chat-br/whatsapp-api/issues) and found none.
+          required: true
+
+  - type: dropdown
+    attributes:
+      label: What type of feature?
+      description: |
+        How to write a good feature request?
+
+        - Respect the issue template as much as possible.
+        - The title should be short and descriptive.
+        - Explain the conditions that led you to suggest this feature: the context.
+        - The context should lead to something, an idea or problem you are facing.
+        - Be clear and concise.
+        - Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown)
+      options:
+        - Integration
+        - Functionality
+        - Endpoint
+        - Database adjustment
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What is the motivation for the request?
+      description: |
+        What problem does the feature seek to solve?
+        Clearly and in detail describe the functionality you want to be implemented.
+        Explain how it fits into the context of the project.
+      placeholder: Detailed description
+    validations:
+      required: true
+  
+  - type: textarea
+    attributes:
+      label: Usage Examples
+      description: |
+        Provide specific examples of how this functionality could be used.
+        This can include scenarios or use cases where the feature would be particularly beneficial.
+      placeholder: text - image - video - flowcharts
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: How should the feature be developed?
+      description: |
+        Should it be inserted directly into the code?
+        Should it be built as a different application that acts as an extension of the API? 
+        For example: a `worker`?
+        
+        Discuss how this new functionality could impact other parts of the project, if applicable.
+
+        ---
+
+        If you have ideas on how this functionality could be implemented, please share them here.
+        This is not mandatory, but it can be helpful for the development team.
+
+      placeholder: Insert feature ideas here
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Additional Notes
+      description: Any other information you believe is relevant to your request.
+      placeholder: Insert your observations here.
+    validations:
+      required: false