Format targets.json to put the items of large lists on their own line

[ghost]

Description

When rebasing a feature branch there are an irritating number of merge conflicts caused by the device_has field in targets.json solely because all features are included on the same line.

The PR formats the targets.json file to include each device feature and similar json lists on a new line to stop this happening so much.

Pull request type

[ ] Fix
[X] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

[kjbracey]

Can't read the diff, but idea is so correct I'm just approving immediately.

[cmonr]

Ever had one of those moments where you think "huh. Why didn't I think of that before?"

[cmonr]

I wonder how many rebases bringing in this PR will cause.

I much prefer this tho.

[0xc0170]

👍 minimize conflicts when touching targets code

Is this updating all labels/macros/device_has ? I noticed some labels were still on the same line. Just checking the "rules" we should follow - if we use "one attribute per line" for all of them.

[kjbracey]

I'm sure I have seen this submitted once before in a PR, but I think the timing was bad - lots of other target changes coming in at the same time.

When you do it, you're going to get the mother of all merge conflicts, so just need to find a moment when there won't be too many other things needing rebasing.

[ghost]

Is this updating all labels/macros/device_has ? I noticed some labels were still on the same line. Just checking the "rules" we should follow - if we use "one attribute per line"

I think I only caught ones that had lines longer than >80. It should be formatted more thoroughly, I'll go back and fix any it missed.

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 3607
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8717/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 3211
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8717/

[mbed-ci]

Test : FAILURE

Build number : 3383
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8717/3383

[cmonr]

Note: This PR is now a part of a rollup PR (#8733).

In order to expidite remaining CI testing, this PR has been bundled into the above rollup PR.

No further work is needed here, as once that PR is merged, this PR will also be closed and marked as merged.

If any more commits are made in this PR, this PR will remain open and have to go through CI on its own.

[adbridge]

This is causing strange merge conflicts with 5.10 so pushing out to 5.11