BLE API does not handle minimum and maximum intervals as in the specification

In the BLE API Gap.h contains the following functions:
- `getMinAdvertisingInterval()`
- `getMinNonConnectableAdvertisingInterval()`
- `getMaxAdvertising interval()`

The Bluetooth v4.2 specification states the following in [Vol 6, Part B] Section 4.4.2.2:

```
The advInterval shall be an integer multiple of 0.625 ms in the range of 20 ms
to 10.24 s. If the advertising event type is either a scannable undirected event
type or a non-connectable undirected event type, the advInterval shall not be
less than 100 ms. If the advertising event type is a connectable undirected
event type or connectable directed event type used in a low duty cycle mode,
the advInterval can be 20 ms or greater
```

Taking this into account, it is not clear from the BLE API documentation what are the differences between `getMinAdvertisingInterval()` and `getMinNonConnectableAdvertisingInterval()`.

Start with Gap.h and the documentation for getMinAdvertisingInterval(), getMinNonConnectableAdvertisingInterval(), and getMaxAdvertising interval(). Compare their intended behavior with Bluetooth v4.2 Vol 6, Part B, Section 4.4.2.2. Done means the API documentation clearly explains the distinctions and the minimum and maximum interval rules.

Written by the indexing model from the issue text.