allow NDEF records with length over 254 bytes

[fanoush]

• use 3 byte length in NDEF TLV block when over 254 bytes
• store 16bit url payload length
• -add maximum lenght checking (type 2 tag data is up to 992 bytes)

this is first attempt to fix #2406 , works for me

[fanoush]

not sure about NDEF and type 2 tag terminology in the comments, feel free to fix/suggest
also the NRF.nfcUrl has some duplicated code with NRF.nfcRaw, it could be done like others - prepare just the payload and pass that to jswrap_nfc_raw

[fanoush]

After splitting jswrap_nfc_raw into two parts the second part can be more easily reused from all other methods without creating extra copy of the payload.

Maybe I should move the nfc_raw_data_start method elsewhere now? at least above the first use so the extra definition is not needed there?

EDIT: and BTW the cleanup saved some code so even with new functionality it is smaller than before (by 136 bytes)
https://github.com/espruino/Espruino/actions/runs/6005580136/job/16288554523?pr=2407#step:3:1137
https://github.com/espruino/Espruino/actions/runs/5903401846/job/16013282040#step:3:1137

[gfwilliams]

This looks great, thanks! Really good news on the space saving too!

Maybe I should move the nfc_raw_data_start method elsewhere now? at least above the first use

That sounds like a good plan - maybe just to where you put the forward decl for now?

[fanoush]

Moved. Also double checked the length check. This works NRF.nfcURL("http://espruino.com?param="+'x'.repeat(959)+'z') and when reading back on phone with NXP TagInfo it fills data area completely and leaves just 16 bytes at the end of the 1024 bytes just as described here https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.0.0/nfc_type2tag_format_dox.html?cp=9_5_7_3_27_1_1 One more character gives Url too long.

[gfwilliams]

That's excellent, thanks! Merging now :)