[ANE-1639] add metadata to vendored dependencies

[jagonalez]

Overview

This PR adds a metadata field for vendored dependencies. This will enable vendored dependencies to be specified with a homepage and description.

Acceptance criteria

A homepage and description is supported for vendored dependencies

Testing plan

• create a directory bar with a vendored dependency
• create a fossa-deps.yaml file like the following:

  
  vendored-dependencies:

• name: metadata-test path: bar/ version: 1.10.0 metadata: homepage: https://fossa.com description: "metadata-test"

• run cabal run fossa -- analyze /path/to/folder
• navigate to the project created in FOSSA, and click on dependencies, if you click on the dependency you should see the homepage and description populated with your values

Risks

n/a

Metrics

n/a

References

https://fossa.atlassian.net/browse/ANE-1639

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.

[doni108don]

• [ ]