Access Token Expires Before Indexing

The asynchronous process of storage record creation and record indexing will sometimes result in records being created but not indexed due to the access token expiring before the index is created. This results in the storage queue being backlogged with un-indexable records, where the GET request from indexer to storage returns a 401 error due to an expired JWT.

Steps to Reproduce:

1. Create a storage record using a valid, but almost expired JWT. The expiration time should be less than the time it takes to index a record. It may be necessary to ingest many records simultaneously and throttle the scaling of indexer-queue/indexer to extend the time of the indexing process.
2. Use search service to verify the record has not been indexed.
3. Check the storage logs to see the 401 response due to the expired token.