Fix bug in detect dynamic deb tatic

[JeffreyHuynh1]

Overview

A bug was introduced in: https://github.com/fossas/fossa-cli/releases/tag/v3.6.15

Deb packages are being marked as rpm due to this line: https://github.com/fossas/fossa-cli/pull/1143/files#diff-4c2f1831b02682e5e64e473c3fefbddfdceba8be7bbb8058539d7c842b06f032R38

As a result, debian packages are being identified as rpm packages.

Acceptance criteria

Ensure that debian packages are correctly identified.

Testing plan

Risks

Metrics

References

• ANE-1604

Checklist

• [x] I added tests for this PR's change (or explained in the PR description why tests don't make sense).
• [x] If this PR introduced a user-visible change, I added documentation into docs/.
• [x] 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.
• [x] 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.
• [x] 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).
• [x] If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.

[jssblck]

@JeffreyHuynh1 when are we merging this? i was surprised to see this issue still occurring