Prompt for "nativeMessaging" permisson inside of a tutorial flow so set up the web server

[Sirs0ri]

The native Messaging part of the BEX (talking to a local webserver) is a very very niche functionality, which has some additional required setup steps. Those steps should be explained properly, and if the user's not interested, there's no need to have the nativeMessaging permission as a required permission.

Idea:

• Make the nativeMessaging optional
• For users that haven't interacted with the nativeMessaging part, show a server tab that holds the config flow
• during the config flow:
  • explain what the nativeMeassaging permission is used to
  • give an early out via "I'm not interested"
  • teach the user how to install/register the native app
  • request the permission
• Store if the user has selected/denied interest in the native part, and adjust the server code accordingly.