Updating LWM2M objects that support CBOR

The resources defined in LWM2M can be of different types. If the resource type is opaque, they cannot be decoded by LWM2M, they are by default converted to Base64. There is an configurable option in LWM2M installer to define if the resource(s) are of CBOR type, so when LWM2M server gets the data from device, it can decode the response and send the data in CBOR format to the callback of registered user.

CBOR_RESOURCES: /?(54321|54399)/([0-9])/[8,9](?:.*)?

The above property defines a regular expression to define that the resources 8, 9 defined in object id's 54321 or 54399 are of type opaque and supports CBOR.