Board data: Fix EMPv2 'many spaces' error
This resolves an EMPv2 parsing bug encountered by @ssummers: The EMP SW puts 4 spaces between the frame number and the first data word. If there are instead 5 spaces between the frame number and the first data word - i.e:
ID: Test
Metadata: (strobe,) start of orbit, start of packet, end of packet, valid
Link 038
Frame 0000 1101 00000fe941781921
Frame 0001 0001 0000000000000000
... then the extra space is currently included in the tokens, causing strobe to be erroneously set to 'False'