When calculating ufsi, the function was relying
on the slot processed by the unicast fhss timer
callback, which can be delayed. When it happens
the slot value is wrong, and the ufsi is incorrect.
The ufsi is then used by the peer to determined
the reply channel, so the devices are thus
unsynchronized until the next uplink packet.
```
connectivity
├── netsocket
├── lwipstack
├── nanostack
│ ├── mbed_lib.json // nanostack-interface's mbed_lib.json
│ ├── include
│ │ └── nanostack // headers from features/netsocket/nanostack-interface
│ ├── source // sources from features/netsocket/nanostack-interface
│ ├── coap-service // used by Thread only - deprecate?
│ ├── mbed-mesh-api
│ ├── nanostack-hal-mbed-cmsis-rtos // HAL porting layer for Nanostack on mbed with CMSIS-RTOS
│ ├── sal-stack-nanostack
│ └── sal-stack-nanostack-eventloop
├── cellular // previously in features/cellular/framework/
├── ...
```
This PR is a part of a wider \connectivity refactoring and implements the above new directory structure for \nanostack.