Decide on how to handle REPLACE in registration
Problem: There are currently two places where registration replacement is defined:
- `registrar-config.yaml` where for each route, it is possible to define its `route.replace`. Additionally `config.defaultReplace=true` from core chart values sets the `route.replace` of all configured routes unless defined specifically for a route.
- ENV variable `REGISTRAR_REPLACE` sets a boolean flag `--replace/--no-replace` CLI parameter for registrar redis daemon, which then sets ALL the `route.replace` to this value
Summarized - currently ENV variable always overrides all the `route.replace` configs for a daemon at runtime, even if ENV var was empty (as in that case, the flag is set to `--no-replace`).
issue