Reports should be JSON formatted

[rosieyohannan]

Currently there is Build Report: at the start of each build report, which I think prevents it from being machine-readable:

Build Report: {
	"partName": "xcvu9p-flgb2104-2-i",
	"lutSummary": {
		"used": 20104,
		"detail": {
			"lutLogic": {
				"used": 16718,
				"available": 1182240,
				"description": "LUT as Logic",
				"utilisation": 1.41
			},
			"lutMemory": {
				"used": 3386,
				"available": 591840,
				"description": "LUT as Memory",
				"utilisation": 0.57
			}
		},
		"available": 1182240,
		"description": "CLB LUTs",
		"utilisation": 1.7
	},
	"moduleName": "reconfigure_io_sdaccel_builder_stub_0_1",
	"regSummary": {
		"used": 54601,
		"detail": {
			"regLatch": {
				"used": 0,
				"available": 2364480,
				"description": "Register as Latch",
				"utilisation": 0
			},
			"regFlipFlop": {
				"used": 54601,
				"available": 2364480,
				"description": "Register as Flip Flop",
				"utilisation": 2.31
			}
		},
		"available": 2364480,
		"description": "CLB Registers",
		"utilisation": 2.31
	},
	"blockRamSummary": {
		"used": 17,
		"detail": {
			"blockRamB18": {
				"used": 32,
				"available": 4320,
				"description": "RAMB18",
				"utilisation": 0.74
			},
			"blockRamB36": {
				"used": 1,
				"available": 2160,
				"description": "RAMB36/FIFO",
				"utilisation": 0.05
			}
		},
		"available": 2160,
		"description": "Block RAM Tile",
		"utilisation": 0.79
	},
	"dspBlockSummary": {
		"used": 0,
		"available": 6840,
		"description": "DSPs",
		"utilisation": 0
	},
	"ultraRamSummary": {
		"used": 0,
		"available": 960,
		"description": "URAM",
		"utilisation": 0
	},
	"weightedAverage": {
		"used": 139369,
		"available": 9067200,
		"description": "Weighted Average",
		"utilisation": 1.54
	}
}

[CampGareth]

@rosieyohannan is this a recent error or a historical one? I thought I fixed this back in this commit: 2f08ac6#diff-ce0151979a0da3cf1233dd0fd63a5aa8

[CampGareth]

Oh, my mistake, that commit is in master but hasn't been part of any release so far. Let's fix that. I've got simulation report support upcoming so we could use that as the trigger for the next release of Reco.