Drop telegraf push from new-minion orch; highstate covers it

New minions run highstate as part of onboarding, which already applies
the telegraf state with the fresh pillar entry we just wrote. Pushing
telegraf a second time from the reactor is redundant.

- Remove the MINION-scoped salt.state block from the orch; keep only
  the manager-side postgres.auth + postgres.telegraf_users provisioning.
- Stop passing minion_id as pillar in the reactor; the orch doesn't
  reference it anymore.

salt/reactor/telegraf_user_sync.sls

@@ -10,8 +10,6 @@
   runner.state.orchestrate:
     - args:
       - mods: orch.telegraf_postgres_sync
-      - pillar:
-          minion_id: {{ data['id'] }}
 
 {% do salt.log.info('telegraf_user_sync reactor: syncing telegraf PG user for minion %s' % data['id']) %}