Suggestion: Safer codal.json for users & create codal.dev.json for development

[microbit-carlos]

The current codal.json:

• Has the "dev" option enabled, that clones the main branch from all libraries, which is a bit risky for the average user. The locked target commits should be safer.
  • Also, changing the value to "false" doesn't actually work, so it can be confusing as well
  • https://github.com/lancaster-university/microbit-v2-samples/issues/63
• Enables debug messages, which are good for debugging, but odd for normal users, who might not expect to see additional data being sent to serial and might not know how to turn it off (it's not really documented anywhere)

This settings are useful for CODAL development, so I suggest to keep them in a new separate codal.dev.json (like codal.ble.json), so that devs can simply mv codal.dev.json codal.json after cloning.

This way we leave a safer codal.json configuration for normal users that might just want to create a CODAL C++ micro:bit programme.

---

This PR also remove the test_ignore key because it's used by build.py only when found in the utils/targets.json file. It probably was accidentally added from copy/pasting the config from utils/targets.json.

Also enables partial flashing on codal.ble.json, which we should probably have on by default.

[JohnVidler]

Suggest we also document this in the README - can this be added to this PR as well?