When someone creates an invalid `queries` entry in the codeql config
file, like this:

```
queries:
  - foo.ql
```

THe error message is confusing, looking like this:

```
  Error: Cannot use 'in' operator to search for 'uses' in ql/ql/src
  TypeError: Cannot use 'in' operator to search for 'uses' in ql/ql/src
      at loadConfig (/home/runner/work/_actions/github/codeql-action/71a8b35ff4c80fcfcd05bc1cd932fe3c08f943ca/lib/config-utils.js:577:41)
```

With this change, the error message is more comprehensible:

`queries must be an array, with each entry having a 'uses' property`

This is no longer needed since `long` now includes its own types.

Mergeback fixes from v1 release

Mergeback v2.1.20 refs/heads/releases/v2 into main

TRAP Caching: Unset missing cache rather than setting to `undefined`

Handle other cases where the config is invalid.

…rror-message

Co-authored-by: Henry Mercer <henrymercer@github.com>

More readable error message for invalid `queries` block and invalid `query-filters` blocl

These were supplying CODEQL_EXTRACTOR_GO_BUILD_TRACING=true rather than
CODEQL_EXTRACTOR_GO_BUILD_TRACING=on,
therefore tracing wasn't being tested.

This is currently broken in CLI versions 2.10.3 and earlier.

It is enough to pass the checks now that we only use the runner for PR
checks.

Fix Go tracing on Windows, and fix tests

Telemetry: Record DB creation time

…nalyzing the default branch.

…edule

When running on a schedule, make a better guess about whether we're analyzing the default branch.