fix: stop rerunning entrypoint-init.bash after first successful start for docker compose

[hahatulk]

Problem: First docker compose up everything is ok
BUT frontend token is corrupted after second docker compose up for docker/compose.yml
Happens always on second time - entrypoint-init resets the frontend_token of frontend.yaml to value │ so frontend cannot get any mappings

Solution: entrypoint-init no more starts every time container is up, only the first time when there is no config generated yet

Example of /var/lib/zrok2/config/frontend.yaml
First start:

v: 1

frontend_token: some_token
identity: public
bind_address: 0.0.0.0:8080
host_match: zrok.domain.com
mapping_refresh_interval: 1m

amqp_subscriber:
  url: amqp://guest:guest@rabbitmq:5672
  exchange_name: dynamicProxy

controller:
  identity_path: /var/lib/zrok2/config/public.json
  service_name: dynamicProxyController

Second start:

v: 1

frontend_token: |
identity: public
bind_address: 0.0.0.0:8080
host_match: zrok.domain.com
mapping_refresh_interval: 1m

amqp_subscriber:
  url: amqp://guest:guest@rabbitmq:5672
  exchange_name: dynamicProxy

controller:
  identity_path: /var/lib/zrok2/config/public.json
  service_name: dynamicProxyController

[vercel]

@hahatulk is attempting to deploy a commit to the OpenZiti Team on Vercel.

A member of the Team first needs to authorize it.