No platform refresh when new platform published

[gsmet]

When I published the new 2.1.1.Final Platform catalog, neither the staging env nor the prod one were automatically updated.

We had:

2021-08-04 14:20:00,118 INFO  [io.qua.cod.ser.PlatformService] (executor-thread-5) PlatformService cache has been reloaded successfully:
    recommendedStreamKey: io.quarkus.platform:2.1 (core: 2.1.0.Final)
    number of extensions: 463

in the logs, whereas the 2.1.1.Final platform was available from the API (at least, I was able to find it in https://registry.quarkus.io/q/swagger-ui/#/Client/get_client_platforms).

{
  "platforms": [
    {
      "platform-key": "io.quarkus.platform",
      "name": "Quarkus Community Platform",
      "streams": [
        {
          "id": "2.1",
          "releases": [
            {
              "version": "2.1.1.Final",
              "member-boms": [
                "io.quarkus.platform:quarkus-bom::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-optaplanner-bom::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-kogito-bom::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-qpid-jms-bom::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-cassandra-bom::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-camel-bom::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-hazelcast-client::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-debezium-bom::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-blaze-persistence-bom::pom:2.1.1.Final",
                "io.quarkus.platform:quarkus-google-cloud-services-bom::pom:2.1.1.Final"
              ],
              "quarkus-core-version": "2.1.1.Final"
            }
          ]
        },

I updated Quarkus to 2.1.1.Final for code.quarkus.io to have something to push to staging and then prod, hoping it will then get the new platform.

[gastaldi]

/cc @aloubyansky @ia3andy

[gsmet]

I had to push a new version to the pods to get the platform refreshed.