[BUG] Fix es_logstash_setup permission error by explicit container user

[rishavtarway]

Change(s)

Change Type: Fixed
Change Category: Internal
Changelog Entry: Fix permission failure in es_logstash_setup by setting an explicit container user in compose.

How to Test

1. Start from a clean checkout.
2. Run docker compose up -d.
3. Verify es_logstash_setup does not fail with permission denied on logstash config generation paths.

Checklist

• Tests have been added or updated to reflect the changes, or their absence is explicitly explained.
• Documentation has been added or updated to reflect the changes, or their absence is explicitly explained.
• A self-review has been conducted checking:
  • No unintended changes have been committed.
  • The changes in isolation seem reasonable.
  • Anything that may be odd or unintuitive is provided with a GitHub comment explaining it.
• All CI checks pass before pinging a reviewer, or provide an explanation if they do not.
• The PR title matches the changelog entry's one-line description.

Explanation for tests/docs: this is a compose runtime permission fix; no Python logic changed. Reproduction/validation steps are provided above.

Related Issues

Closes #224

[rishavtarway]

This PR intentionally changes only docker-compose.yaml (es_logstash_setup user) to avoid broad chmod/chown host workarounds discussed in #224. If preferred, I can also test and include the same explicit user in docker-compose.dev.yaml.

[rishavtarway]

Validation update: I built aiod_metadata_catalogue, created a local src/config.override.toml for the bind mount expected by compose, and verified targeted startup path (elasticsearch + es_logstash_setup) succeeds with this change. PR scope remains intentionally limited to the es_logstash_setup user configuration for #224.

[rishavtarway]

Quick status update on this PR:

• Scope remains intentionally limited to docker-compose.yaml (es_logstash_setup user).
• Local validation completed for the targeted path:
  • docker compose up -d
  • Verified es_logstash_setup no longer fails with permission-denied during logstash setup.
• No unrelated files are included in this change.