Consider Changing Dev Strider KP-Registry

[uhbrar]

Currently, when running a dev instance of strider locally, we have it also spin up a local version of the kp-registry. Is there a good reason to be doing this? I think it might be more advisable for it to default to a deployed version of the KP-registry, and I'm not really sure why we would have it point to a locally running version. The version that strider runs locally is fairly out of date anyway, which is why this might be a concern.

[cbizon]

I seem to recall that when running locally in the container that it points to the prod registry? I think that there is/should be an environment variable.