Adds title lint config and removes old PRLint config (#659)

Signed-off-by: Marcos Iglesias Valle <golodhros@gmail.com>

.github/PULL_REQUEST_TEMPLATE.md

-<!--- 
-Provide a general summary of your changes in the Title above 
-Include a prefix to the title, one of build|ci|docs|feat|fix|perf|refactor|style|test|chore|other followed by a colon. 
+<!---
+Provide a general summary of your changes in the Title above
+Include one of these prefixes:
+  fix – Fixes an unexpected problem or unintended behavior
+  feat – Adds a new feature
+  docs – A documentation improvement task
+  build – A task related to our build system
+  ci – A task related to our ci system
+  perf – A performance improvement
+  refactor – A code refactor PR
+  style – A task about styling
+  test – A PR that improve test coverage
+  chore – A regular maintenance chore or task
+  other – Any other kind of PR
+
 Example: docs: Improves the documentation on...
 -->
+
 ### Summary of Changes
-<!-- Include a summary of changes -->
 
+<!-- Include a summary of changes -->
 
 ### Documentation
-<!-- What documentation did you add or modify and why? Add any relevant links -->
 
+<!-- What documentation did you add or modify and why? Add any relevant links -->
 
 ### CheckList
+
 Make sure you have checked **all** steps below to ensure a timely review.
+
 - [ ] PR title addresses the issue accurately and concisely, including a title prefix.
 - [ ] PR includes a summary of changes.
 - [ ] My commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)"

.github/prlint.json

-{
-  "title": [
-    {
-      "pattern": "^(build|ci|docs|feat|fix|perf|refactor|style|test|chore|other)((.+))?:\\s.+",
-      "message": "Your title needs to be prefixed with a topic."
-    }
-  ],
-  "body": [
-    {
-      "pattern": ".{1,}",
-      "message": "You need literally some contents in your description"
-    }
-  ]
-}

.github/titleLint.yml

+regex: (build|ci|docs|feat|fix|perf|refactor|style|test|chore|other): .*