[ANE-699] Analysis discovery filter should be applied prior to analysis

[meghfossa]

Overview

This PR,

• Makes default non-production path filtering prior to analysis stage

Currently, discovery path filters are applied at walk', so we don't even discover the targets, but for non-production path filtering
I did not choose this approach, as we still want to show that we intentionally skipped this discovered targets in scan summary. If,
we choose to apply non-production path filtering at walk' stage - users won't know why certain projects were skipped.

Acceptance criteria

• Targets in default non-production path (e.g. /docs, .git/, etc.) should not be analyzed

Testing plan

Here is the directory structure (zip attached) for filesystem, and (sandbox/container.tar) for container.
sandbox.zip

.
├── Dockerfile
├── backend
│   ├── docs
│   │   └── reqs.txt
│   └── util
│       └── example
│           └── reqs.txt
├── container.tar
├── docs
│   └── app
│       └── reqs.txt
└── reqs.txt

7 directories, 6 files

0. git pull origin && git checkout feat/non-prod-path-discovery-filters && make install-dev
1. fossa-dev analyze <extracted-zip-dir> -o | jq
2. fossa-dev container analyze <extracted-zip-dir/container.tar> -o | jq

For both of this you should see only 1 source unit manifest for reqs.txt

Risks

N/A

References

ANE-699

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 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. 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).

[spatten]

👍 Looks good to me!