bug: ids.authority.wait-time=3000 does not have any effect at all

Hi team,

ids.authority.wait-time=3000 does not have any effect at all .The system still uses the default value of 300 ms. This needs to be fixed so that the configured value is respected.

For confirmed bugs, please report:

- Version: 1.2
- Storage Backend: Cassandra

```
org.janusgraph.diskstorage.TemporaryBackendException: Wrote claim for id block [1600001, 2000001) in PT0.494402S => too slow, threshold is: PT0.3S
at org.janusgraph.diskstorage.idmanagement.ConsistentKeyIDAuthority.getIDBlock(ConsistentKeyIDAuthority.java:284)
at org.janusgraph.graphdb.database.idassigner.StandardIDPool$IDBlockGetter.call(StandardIDPool.java:281)
at org.janusgraph.graphdb.database.idassigner.StandardIDPool$IDBlockGetter.call(StandardIDPool.java:248)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
```

Start at ConsistentKeyIDAuthority.java:284, then trace how ids.authority.wait-time is read and passed into the ID block claim logic. Reproduce with the Cassandra storage backend and the setting at 3000 ms; done means the configured threshold is used instead of the default 300 ms and the reported exception no longer reflects the default.

Written by the indexing model from the issue text.