repeater option: repeat all scopes

[dl9sau]

With firmware <= 1.9 (thus before invention of scopes), repeaters repeat all scoped messages.
There are reasons for still providing this feature (default: no), i.E.

• less config overhead for new users with their house repeater who have only scoping repeaters around (which drop wrong scopes anyway).
• Some admins dislike scopes. They currntly use old firmware by intent. This prevents new features like multibyte-path, new loop detection and maybe other important protocol/behavior fixes. Or they update to current version and ignore scoped messages (vice versa is recommended), and only repeat unscoped (adverts, channel messages and DMs). So in case of channel messages, they repeat the (to the network) more harmful unscoped messages and block the good ones (scoped messages).

If enabled, those repeaters must not reply to scope discovery of users, because region list may be outdated or not configured.

[dl9sau]

A more visual example:

Repeaters A1.14 and C1.14 with firmware 1.14 and scope de-be

user1 - A1.14 - B1.09 - C1.14 - user2

User sends scoped: ok
User sends unscoped and allow * F at A and B: ok
user sends unscoped and deny * F at A or C: block at A or C as intended
User sends with multibytepath: blocks at B

user1 - A1.14 - B1.14noScopeConfigured - C1.14 - user2
User sends scoped: block at B
User sends unscoped and allow * F at A, B and C: ok
user sends unscoped and deny * F at A, B or C: block at A, B or C as intended
User sends with multibytepath: ok

user1 - A1.14 - B1.15noScopeConfiguredButScopesPass - C1.14 - user2
User sends scoped: ok
User sends unscoped and allow * F at A, B and C: ok
user sends unscoped and deny * F at A, B or C: block at A, B or C as intended
User sends with multibytepath: ok

Note:
B1.15noScopeConfiguredButScopesPass blocks ‚direct‘, as suggested in
#2029