v1.2.0

LWM2M Off by Default

The LWM2M functionality will now be disabled by default on all Skywire Nanos. Any existing Skywire Nano that is updated to this version will automatically have its LWM2M turned off.

Fixes/Changes from v1.1.0

LWM2M Network Connection Loop Fix

In previous versions of the Skywire Nano firmware, in certain circumstances the LWM2M operation could get into a looping mode where it issues AT+CFUN=4 and then AT+CFUN=1 rapidly and continuously. This stems from a pre-shared key being erronously deleted. This key will no longer be deleted, and the looping state should no longer occur.

AT Commands

The AT#LWM2M command will now accept a parameter to disable LWM2M functionality in the "set" usage. The setting will be retained between power cycles, and thus only needs to be run once.

To disable LWM2M, issue:
```
AT#LWM2M=0
```
To enable LWM2M, issue:
```
AT#LWM2M=1
```
The AT#LWM2M command's response output has three changes:

1) The output will now include a #LWM2M: prefix

2) The <state> output will now be inside of quotation marks

3) The enabled/disabled status will now be displayed in addition to <state>

The "read" command response takes the form:
```
AT#LWM2M?
#LWM2M: <enabled>,"<state>"
OK
```

Known Issues

Using a hostname for a TLS secure socket will result in a memory leak in the Nordic co-processor firmware, resulting in a likely system hang after ~22 iterations of socket opening, connecting, and closing. The TLS credentials ("tags") can still be used.
".noinit" linker sections for RAM will not work properly in application firmware
The MQTT client in the AT interface firmware does not support hostname verification
No DFU URC is generated when stopping using either AT#XFOTA=0 or AT#FWUPD=0
The AT%XMAGPIO set command does not work and returns an error