Make max Scanner count limit user configurable

[damnMeddlingKid]

We are trying to run hyperscan in an Apache Beam streaming pipeline. We read from many different Kafka topics on our workers so we have many inflight threads. The 256 Scanner count limit is quite restrictive in this environment even when one scanner is created per thread. It would be great if it could be configured by users or find an alternative solution for the callback allocation.