Tweak Vendetta source dep data format

[nficca]

Overview

Tweaking the format that vendored dependency data is sent. Instead of a single object with a type and path field, we are now sending a list of a single object with a type and path field. This is to align with changes that have been made to support the same dependency being vendored under multiple paths in the same code base.

There are no user facing changes.

Acceptance criteria

• Vendored dependency data can be successfully sent to FOSSA

Testing plan

Built this branch and ran it against the latest version of FOSSA, successfully saw dependencies sent across

Risks

The --x-vendetta flag is still experimental and this should not effect anything else.

Metrics

No additional metrics.

References

https://fossa.atlassian.net/browse/CORE-6302

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.