Issue Reporter: Missing data - configuration options, active extensions details

User story

As a filter list author (internal or external) reviewing the submitted issue reports, I need information on the user's configuration details, filters applied and other extensions included in the issue report so that I can better troubleshoot issues.

(Note: these were available in the old issue report)

Background

1. Configuration options
   1. Ad blocking enabled?
   2. Cookie behavior
   3. Element collapsing enabled?
   4. Filter list auto-updates enabled?
   5. JavaScript enabled?
   6. Object tabs enabled?
   7. Private browsing
2. Warnings and errors (to be resolved by #155 (closed))
   1. Column
   2. File
   3. Line
   4. Source line
   5. Text
   6. Type
3. Active extensions and Plug-Ins (as opt-in)
   1. ID
   2. Name
   3. Type
   4. Version
4. Other
   1. Platform build ID (e.g. 20170509074737)
   2. Window
      1. Opener
      2. Referrer

The ones that are crossed out only apply to the legacy version of the extension due to differing sets of features.

What to change

Update the issue report according to:

1. Spec here

Todo:

• Add design for opt-in feature for Private Browsing (1.2), Javascript Enabled (1.5), Cookies (1.7), and other extensions (3)- @naser
• Define text for opt-in feature - @lisabielik
• Update specs https://gitlab.com/eyeo/specs/spec/merge_requests/188 - @jeenlow / @ThomasGreiner
• Translate text for feature - @amazurek @Shikitita
• Privacy policy / T&Cs update check - @Zarillo
• Legal LGTM - @Zarillo

Integration notes

• Add optional permissions to metadata.chrome:
  • contentSettings
  • management
• Import adblockplusui/proxy.html.
• Add asynchronous browser API to polyfill.js:
  • permissions.contains
  • permissions.remove
  • permissions.request

See https://gitlab.com/eyeo/adblockplus/abpui/adblockpluschrome/merge_requests/15/diffs.

Hints for testers

See trac#7106.