add issue templates and dependabot

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

@@ -0,0 +1,21 @@
+---
+name: "Bug report \U0001F41E"
+about: Create a report to help us improve
+
+---
+
+## Description
+
+Describe the issue that you're seeing.
+
+### Steps to reproduce
+
+Clear steps describing how to reproduce the issue. Please please please link to a demo project if possible, this makes your issue _much_ easier to diagnose (seriously).
+
+### Expected result
+
+What should happen?
+
+### Actual result
+
+What happened.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,4 @@
+contact_links:
+  - name: Question 🙋
+    url: https://github.com/jptosso/coraza-waf/discussions/categories/q-a
+    about: Ask your question in Coraza WAF Discussions

.github/ISSUE_TEMPLATE/feature-request---.md

@@ -0,0 +1,17 @@
+---
+name: "Feature request \U0001F680"
+about: Suggest an idea for Coraza WAF
+
+---
+
+## Summary
+
+Brief explanation of the feature.
+
+### Basic example
+
+Include a basic example or links here.
+
+### Motivation
+
+Why are we doing this? What use cases does it support? What is the expected outcome?

.github/dependabot.yml

@@ -0,0 +1,11 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "gomod" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "daily"