Emesary damage system chokes on certain callsigns

[NikolaiVChr]

If AI callsign is longer than 7 chars, it will mess up the notifications, and armamentInFlight flags (thrust and active-radar) will be random values.

If callsign contain space it will not match since emesary removes that under decoding and hit notifications will not work.

Note to self: left("Niko", 7) == nil

[NikolaiVChr]

I suspect this issue is related to #475

[NikolaiVChr]

Pilot testimony: well, for example as from what i tested with him. today earlier, XXX and four numbers works well for his FlightGear, but XXXXX and 2 numbers not works. Also it works better without 0s, just bigger numbers... its very strange for example XXXXX07 not works while XXX1221 works perfectly

[NikolaiVChr]

4f893d48427a574c042ccefad2269c941ae8ea44 attempts to fix this

[NikolaiVChr]

It seems fixed, but keeping this issue open, so we don't forget this issue in future commits that communicate with emesary.