Add menu to report bug and rendering issues

# Issue details

### Duplicate?
Have you searched the issues of this repository if your issue is already known? yes

### Actual behaviour
When I find a bug (including this one, how meta) or something reportable (such as a content rendering issue), I need to go to the github page manually, and create a bug there.

### Expected behaviour
It would be good to have a direct link to the new issue template, ideally prepopulated with environment details and logs

# Steps to reproduce the issue
1. Find a bug, or rendering issue
2. Go to the side menu of the app in search of a “report issue”, or “report rendering issue” in article view
3. Can't find
4. Open the browser to https://github.com/wallabag/android-app/issues/new manually, and be sad

# Environment details
- **wallabag app version**: 2.0.2 (106)
- **wallabag app installation source** (e.g. Gplay, F-Droid, manual): F-Droid
- **Android OS version**: 7.1.2
- **Android ROM** (e.g. stock, LineageOS, SlimRom,…): LineageOS 14.1
- **Android hardware**: Hammerhead
- **wallabag server version**: 2.3.2
- **Do you have Two-Factor-Authentication enabled?**: no
# Your experience with wallabag Android app

Have you had any luck using wallabag Android app before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)

Yup, works great :+1:

Start by locating the side menu and article view entry points in the Android app, then inspect the new-issue template at the linked GitHub URL. Determine how those screens could expose separate reporting links and which environment details or logs are available to prepopulate. Done means both report paths are reachable and produce a useful prefilled issue.

Written by the indexing model from the issue text.