Overview

Fixes a broken link, Docs-only change.

Acceptance criteria

The user is directed to the appropriate section

Testing plan

I clicked the link to verify it was correct.

• https://github.com/fossas/fossa-cli/blob/fix-broken-default-filter-link/docs/references/subcommands/analyze.md#filtering-paths-and-targets
• https://github.com/fossas/fossa-cli/blob/fix-broken-default-filter-link/docs/references/subcommands/analyze.md#why-is-the-fossa-cli-skipping-my-project

Risks

Low risk, link was broken. Docs-only change.

Checklist

• I added tests for this PR's change (or explained in the PR description why tests don't make sense).
• If this PR introduced a user-visible change, I added documentation into docs/.
• If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
• If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an ## Unreleased section at the top.
• If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
• If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.