Use tags to assign responses to result list

[zack13532]

Previously, when asynchronously processing responses for a GetFeaturesBatch request (resulting in many individual GetFeature calls), we searched for the request object in the original request list to determine where to place the response in the response list, so as to maintain ordering. This is less efficient than it could be, because it is a linear search on an ArrayList using the Request object's equals method.

Instead, use the OkHttp tags feature for Calls to store the index as metadata that can be retrieved during response processing, so we can use that directly rather than doing a search.

[zack13532]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Enqueue calls with the OkHttp client's ExecutorService #93 : 2 dependent PRs (#94 , #97 )
• Pass index into callback #96
• Set request index as a header #95
• Use tags to assign responses to result list #92 👈 (View in Graphite)
• Remove usage of parallelStream in favor of stream #91
• Update changelog for 0.9.2 #90
• Update readme with usage examples and bump version #89
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.