docs(plugins.development): keep sync-code running while resolving conflicts

[khaito241]

What

Add a guidance bullet to the setup-amql-development skill: when markers), resolve them in place and keep the sync running, don't stop it to resolve and restart.

Why

Conflicts during sync are a normal part of reconciling local and cloud code. The observed bad pattern was the agent treating a conflict as an error: stopping sync-code, resolving the markers, then restarting it.

That's wrong because:

• Stopping and restarting re-compares cloud vs local, finds them divergent again, and re-triggers the same conflict -> an endless loop.
• A running sync pushes the local resolution up to cloud, which is what actually settles the conflict.

Keeping the sync running lets the local fix propagate and resolve cleanly.

Changes

• plugins/holistics-development/skills/setup-amql-development/SKILL.md -> one sub-bullet under the sync-code --background usage line.