refactor(perf): change aiDoCommand to take non-const pointer for move semantics

[bobtista]

• Merge before Use move for std::vector instead of copying in path functions #1895

Refactors aiDoCommand and AICommandParmsStorage::store to accept non-const pointers/references, enabling move semantics optimization.

Changes:

• Changed aiDoCommand signature from const AICommandParms* to AICommandParms* across all implementations
• Updated AICommandParmsStorage::store signature from const AICommandParms& to AICommandParms&

[xezon]

Modified store implementation to use move_or_swap for m_coords instead of copying

Where is that? I do not see.

[bobtista]

Modified store implementation to use move_or_swap for m_coords instead of copying

Where is that? I do not see.

I removed it, I think it should be done in 1895 not here. I updated the description

[Mauller]

I think in this instance it's one of those times where i would say using const cast at the point where removing constness is required would be a better option.

Keeping the command considered const keeps that contract that we shouldn't be changing the data of the command and only consuming it.

i would then also put a comment on why we const cast that particular data.