fix(deployable): update remote service config on push for static envs

[vigneshrajsb]

Summary

• When a push to a service repo (e.g. consumer-mcp) triggers a rebuild of a static env (good-dev-0) via trackDefaultBranches, the previous guard in updateOrCreateDeployableUsingYamlConfig skipped all remote services when filterGithubRepositoryId was set — including the service that triggered the push
• This left stale deployable config (e.g. helm.grpc:true) even after the source lifecycle.yaml was updated
• Fix resolves filterGithubRepositoryId to a repo name once before the loop, then skips only remote services whose repo name does not match — so the triggering service is re-read and patched correctly

Root cause (PR #84 regression)

PR #84 changed importYamlConfigFile from being skipped entirely on push events to always running with a filter. The filter guard was written as if (filterGithubRepositoryId) return which skips every remote service, including the one that changed.

Test Plan

• Push a commit to a service repo tracked by a static env with trackDefaultBranches=true — verify the deployable's helm config is updated
• Confirm other remote services in the static env are still skipped (check debug logs: Skipping remote YAML fetch for filtered deploy)
• Selective redeploy of a remote service in a static env updates its deployable config
• PR env pushes unaffected (services are local to the PR repo, never hit the remote guard)

🤖 Generated with Claude Code