fix(seed-dev): remove invalid --env flag from cypher-shell invocation

[pgrisales]

Summary

Removed invalid --env flag from the direct cypher-shell invocation in
infra/scripts/seed-dev.sh. The flag is not recognized by cypher-shell and
caused the seed script to fail. The password is already exported to the
environment via export NEO4J_PASSWORD before the call, so cypher-shell
picks it up automatically from the environment — no flag needed.

Release metadata

Release note (PT-BR): Corrigido erro no script de seed do Neo4j causado por flag inválida --env no cypher-shell.
Release note (EN): Fixed Neo4j seed script failure caused by invalid --env flag in cypher-shell invocation.
Release highlights (PT-BR, bullets with |): | Correção do script seed-dev.sh para ambiente de desenvolvimento
Release highlights (EN, bullets with |): | Fix seed-dev.sh script for development environment
Included pattern IDs (comma-separated, or none): none
Technical changes (PT-BR, bullets with |): | Removida flag --env NEO4J_PASSWORD inválida da chamada direta ao cypher-shell
Technical changes (EN, bullets with |): | Removed invalid --env NEO4J_PASSWORD flag from direct cypher-shell call
Change type (choose one release label from taxonomy):

Change type (choose one release label from taxonomy):

• release:major
• release:feature
• release:patterns
• release:api
• release:data
• release:privacy
• release:fix
• release:docs
• release:infra
• release:security

Breaking change?

• No
• Yes (describe migration/impact in summary)

Validation

• Local tests/checks passed for impacted scope
• CI and Security checks are green
• Exactly one release label is set on this PR

Public safety and compliance checklist

• No personal identifier exposure was introduced
• PUBLIC_MODE behavior was reviewed (if relevant)
• Public boundary gate is green
• Public endpoints and demo data contain no personal data fields
• Legal/policy docs were reviewed for scope-impacting changes
• Snapshot boundary remains compliant with docs/release/public_boundary_matrix.csv

Risk and rollback

Risk: Minimal — single line removed from a dev-only seed script. No
production code or data is affected.

Describe key risks and how to roll back if needed.

Rollback: Revert this commit. The script will fail again with
unrecognized arguments: '--env' but no data or services are impacted.