Druid jdbc lookups: why poll period isn't working?

Hey, I created a lookup and was hoping that it will update within given time range
But actually it's not (data remains the same )

Here is what specified in the config.
```

{
"type": "cachedNamespace",
"extractionNamespace": {
"type": "jdbc",
"connectorConfig": {
"connectURI": "someuri",
"user": "someuser",
"password": "somepass"
},
"table": "sometable",
"keyColumn": "somekey",
"valueColumn": "somevalue",
"filters": "not thing_name is null"
},
"firstCacheTimeout": 0,
"pollPeriod": "PT5M",
"injective": true
}

```

Also I tried to create a lookup from example located [here](https://druid.apache.org/docs/latest/development/extensions-core/druid-lookups.html#example-of-polling-on-heap-lookup)

It looks like

```
{
"type": "pollingLookup",
"pollPeriod": "PT10M",
"dataFetcher": {
"type": "jdbcDataFetcher",
"connectorConfig": "someuri",
"table": "sometable",
"keyColumn": "somekey",
"valueColumn": "somevalue"
},
"cacheFactory": {
"type": "onHeapPolling"
}
}

```

First config is creating a lookup which is not updating
Second one (straight from the docs) doesn't appear in the lookup schema at all (telling that this lookup does not exist)

Can someone help and answer what is missing?

Compare the cachedNamespace and pollingLookup configurations with the linked polling-on-heap lookup documentation, focusing on the JDBC settings and pollPeriod behavior. Confirm why the first lookup does not refresh and why the second is absent from the lookup schema; done means identifying the missing or incorrect configuration and documenting the expected behavior.

Written by the indexing model from the issue text.