NFC_EEPROM sample write does not take effect on NUCLEO-L433RC-P + X-NUCLEO-NFC04A1

### Description of defect
After building the NFC_EEPROM sample for the Nucleo-L433RC-P dev board with the Nucleo-NFC04A1 expansion, the sample compiles and runs, but while it claims to successfully write a message, the message in the EEPROM is not modified.

The following was added to `mbed_app.json` in `target_overrides`:
```
"NUCLEO_L433RC_P": {
"target.extra_labels_add": ["ST25DV"],
```

After compiling and flashing, the following output is observed:
```
Building an ndef message
message written successfully
Received an ndef message of size 20
message read successfully
```

However, the message when read by a smartphone remains unchanged - and no matter the URL set in the source, the length read back is always 20.

#### Target(s) affected by this defect ?
NUCLEO-L433RC-P + X-NUCLEO-NFC04A1

#### Toolchain(s) (name and version) displaying this defect ?
Arm Compiler 6

#### What version of Mbed-os are you using (tag or sha) ?

6.15.1

#### What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
None

#### How is this defect reproduced ?
1. Download this repository and open it as a workspace in Mbed Studio
2. Select the NFC_EEPROM project as active
3. Make the changes described above to `mbed_app.json`
4. Compile and run the app.

Reproduce the issue in the NFC_EEPROM project on the NUCLEO-L433RC-P with the X-NUCLEO-NFC04A1, using the target override in mbed_app.json. Compare the reported write and read results with the message observed on a smartphone, and trace the sample's write/read flow. Done means the configured URL is written to EEPROM and the read-back length and smartphone content match it.

Written by the indexing model from the issue text.