[FR] Improve query processing performance and output for SentinelOne

Which category is the feature part of?

Add error processing for PQ to avoid queries hitting the total character limit of a query which is 8192 characters.
Improve multithreading performance for DV queries while still respecting the 60 second query limit. Fetching data can happen concurrently as queries are kicked off every 60 seconds in this way.
Improve output by grouping queries by their tag to appropriately display output for each tag in the results.

Changes include:

Add error processing to evenly split up queries that are approaching the maximum query limit of characters. An approach of using 75% of the character limit is used in order to account for any additional characters outside of the terms themselves and if any additional columns are added to outputs in the future. This may need to be adjusted later if major changes to columns outputs are made.
multi-threading was enabled for all query types. When DV is being used the logic was moved to handle kicking off the requests every 60 seconds in order to avoid race conditions of the logic from queued up queries in the concurrent.futures method.
processing was added to group queries for both PQ and DV by tags. For PQ, this increases the efficiency as before all queries ran 1 at a time. For DV, this can decrease efficiency due to not bundling queries in groups of 10, but it greatly improves the output results with more easily identifying which result is associated with which tag. These changes primarily affect the use of definition files.