region default command unexpected results

[f3sty]

I ran into two unexpected results from the 'region default' command while configuring repeaters.

1. 'region default' followed by two space chars sets the last region in the region table as the default scope.
   If this was a flood denied region, it gets silently changed to allow flood.

2. 'region default' followed by a single space should remove any configured default region scope (if I am interpreting the docs correctly) but instead returns the currently configured default scope.

I've replicated these results on repeaters running 1.15 and 1.16.
I initially hit these issues while using Remote Terminal, but have confirmed that these commands sent via the official Meshcore app produce the same results (but setting/clearing via the Meshcore app UI works as expected).

Example:
([CR] denotes carriage return / hitting 'send' etc, included below to show the trailing whitespace chars clearly)

List regions configured, last entry is a deny flood:

> region[CR]
*^ F
 au F
 au-nsw F
 au-nsw-syd F
 syd F
 nsw F
 au-nsw-wsi F
 test-deny

Confirm no default region is configured:

> region default[CR]
 default scope is <null>

Send 'region default' + 2 space chars - unexpected scope now set:

> region default  [CR]
 default scope is now #test-deny

List the configured regions, flood has been modified on the last entry:

> region[CR]
*^ F
 au F
 au-nsw F
 au-nsw-syd F
 syd F
 nsw F
 au-nsw-wsi F
 test-deny F

Send 'region default' plus one space char, which should clear the default scope but instead just reports the currently configured default:

> region default [CR]
 default scope is #test-deny