Update DFE Query Building Logic

[rc-csmith]

Changes

• Since DFE sorts telemetry types into separate tables, we only need to query one table when processing definition files
• For individual queries, they should be free-form and allow the user to search/join/union whatever they need to.
• Added spec tests for DFE product to ensure queries are formed as expected
  • build_query() formats supported filter options correctly
  • build_query() gracefully handles unsupported filter options
  • process_search() does not alter the given query
  • nested_process_search() parses a definition file as expected
  • nested_process_search() gracefully handles unsupported definition file fields
  • process_search() correctly appends filter options
• Add GitHub Workflow to automatically run tests for pull requests/pushes to any branch

Caveats that need to be documented:

• Unlike prior versions, this allows users to provide a complete query without any constraints. That being said, there are four required field names that must be projected in those user-defined queries otherwise the resulting CSV will be empty or have incomplete data:
  • DeviceName
  • AccountName or InitiatingProcessAccountName
  • ProcessCommandLine or InitiatingProcessCommandLine
  • FolderPath or InitatingProcessFolderPath
• Users can now specify either a token or the tenantID, clientID, and clientSecret in the credential file

Closes #99

Closes #109

Related to #81