Remove subscription check on fossa report preflight check

[JeffreyHuynh1]

Overview

fossa report fails for free tier users. This shouldn't be the case with the changes to our free plan: https://fossa.com/blog/secure-open-source-fossa-upgraded-free-plan/ . We are currently failing because our preflight checks for fossa report are still configured to check if users have a premium subscription type. Remove this preflight check to account for FOSSA's free plan changes.

Slack threads:

• https://teamfossa.slack.com/archives/CCPE2LSRL/p1726587987001969
• https://teamfossa.slack.com/archives/CCPE2LSRL/p1726592473411099?thread_ts=1726587987.001969&cid=CCPE2LSRL

Acceptance criteria

• fossa report works for free tier users

Testing plan

With a free tier account, do the following:

• fossa analyze
• fossa report attribution --format html

Risks

Metrics

References

• ANE-2048

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.

[zlav]

This looks safe. The only real change I see is that we no longer check subscription type before someone runs the report command.