Integrate support for Sentry reporting

[4lovi4]

What do these changes do?

sentry integration template for the generated app

Are there changes in behavior for the user?

Related issue number

Closes #120

Checklist

• [ ] I think the code is well written
• [ ] Unit tests for the changes exist
• [ ] Documentation reflects the changes
• [ ] Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> (e.g. 588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the PR
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

[Arfey]

It's look as very useful feature for a lot of people. If we want that people use this then we need to describe about that for them.

• [ ] add description about this flag to the readme
• [ ] add description about setting sentry to the documentation

@4lovi4 can you do that? 😀

[4lovi4]

Going to refresh the doc.

[webknjaz]

@4lovi4 any updates?

[Arfey]

@4lovi4 any updates 2.0?)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}