Thanks to @aibaars, `path.resolve()` should will nicely handle more use-cases, namely absolute paths better than `path.join()`.

Co-authored-by: Arthur Baars <aibaars@github.com>

Previously, I had tried to refer to '${{ github.workspace }}', but that caused a problem in Actions. Trying to avoid the issue, I changed this to "the workspace," but this gives up quite a bit of specificity.

Co-authored-by: Arthur Baars <aibaars@github.com>

It causes the action to break (or rather that context being unavailable causes it to fail), despite it being in the description field.

In the previous commit, the default value of the input is ${{ github.workspace }}
which means that most uses of this input would probably prefix their paths with
${{ github.workspace }}, especially since actions/checkout's 'path' input
must be under ${{ github.workspace }}. Therefore, it doesn't make much sense for
this to be an absolute file path.

Instead, it's more intuitive to make this relative to the repository.

This input is exposed in the CodeQL CLI as the flag --source-root, allowing
users of the CLI to set --source-root different from --working-dir. However,
in codeql-action, these two paths are conflated and it poses problems for
users with complicated build environments, in which a source root may be
a child of the working directory.

Most users should not notice this, as the default value is
${{ github.workspace }}, as it is implied now (`path.resolve()`).

Allow local instead of downloaded CodeQL

Support splitting of DB creation and query execution

Run tests against nightly CLI bundles

Allow  to be run on workflow_dispatch

Mergeback v1.0.4 refs/heads/v1 into main

Update readme to include section on missing analysis

Merge main into v1

Add new `packs` input to init action

Fixes #598

Also, update the options and inputs documentation.

…ssing

Restore original getCodeQLActionRepository behaviour