saveMissionProfileNamespace is inconsistent when running on a Linux server.

Sometimes it successfully writes to the file, sometimes it doesn't. In all cases it returns true. Repeatedly calling it seems to make no difference.

This means we can set variables on the missionProfileNamespace, call saveMissionProfileNamespace, and later reload the mission and all data that should have been there wasn't present.

We found that saveProfileNamespace seemed to flush the saveMissionProfileNamespace write to the disk, but not consistently either.

saveProfileNamespace seems to work consistently - no issues there.