Deployment platform-related code not respecting new method signature

The following discussion from !5127 (merged) should be addressed:

• @mikegreiling started a discussion:

  This change appears to have broken my GDK instance. I started getting the following error:

  17:03:56 postgresql.1            | ERROR:  operator does not exist: character varying = integer at character 217
  17:03:56 postgresql.1            | HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.
  17:03:56 postgresql.1            | STATEMENT:  SELECT  "clusters".* FROM "clusters" INNER JOIN "cluster_projects" ON "clusters"."id" = "cluster_projects"."cluster_id" WHERE "cluster_projects"."project_id" = $1 AND "clusters"."enabled" = $2 AND (environment_scope IN ('*', 29) OR
  17:03:56 postgresql.1            |       29 LIKE
  17:03:56 postgresql.1            |         REPLACE(REPLACE(REPLACE(environment_scope,
  17:03:56 postgresql.1            |                             '%', '\%'),
  17:03:56 postgresql.1            |                     '_', '\_'),
  17:03:56 postgresql.1            |             '*', '%')
  17:03:56 postgresql.1            |     
  17:03:56 postgresql.1            |     )  ORDER BY CASE environment_scope
  17:03:56 postgresql.1            |       WHEN '*' THEN 0
  17:03:56 postgresql.1            |       WHEN 29 THEN 2
  17:03:56 postgresql.1            |       ELSE 1
  17:03:56 postgresql.1            |     END DESC LIMIT 1

  it worked again after I changed environment back to environment.name. any idea why? not sure if this was a quirk of my GDK instance or a legitimate bug.