[No Ticket] Fix "Property name is not allowed" error for RPM deps

[gilfaizon]

Overview

This PR should hopefully fix a tiny issue with the fossa-deps schema that's been bugging me for some time.

When using a fossa-deps.yml file with an RPM dependency, the "name" field would be deemed invalid.

Acceptance criteria

No more squiggly red lines! Names are valid, and should be considered as such.

Testing plan

With JSON and YAML Schema Download enabled in VSC, create a fossa-deps.yml file with the following:

referenced-dependencies:
- type: rpm-generic
  name: cpio
  os: sles
  osVersion: "15.4"
  arch: x86_64
  version: 0:2.13-9.fc34

Open the file in VSC, it should inform you that "Property name is not allowed"

After checking out this branch, or downloading the fossa-deps.schema.json file:

1. Open your VSC Settings
2. Search for "Schema"
3. Select "Yaml: Schemas" > "Edit in settings.json"
4. Add the following:

"yaml.schemas": {
            "file:/path/to/folder/fossa-cli/docs/references/files/fossa-deps.schema.json": "fossa-deps.yml"
        }

Risks

I'm not sure if I need to change anything else, can reviewers please confirm whether I need to modify any additional files to reflect the change?

I also don't know if this will actualy fix the issue! Tested locally, but unsure what needs to be done for the changes to propagate.

References

No references.

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

[CLAassistant]

All committers have signed the CLA.

[jssblck]

lgtm, but please make an entry in the changelog. Just do something like this, and we'll bundle it in the changelog of the next versioned release:

### Unreleased

- Doc only: fixed issue in `fossa-deps` schema preventing use of `name` for referenced RPM dependencies [#1199](https://github.com/fossas/fossa-cli/pull/1199).

I don't think we propagate these files anywhere else, I think we just provide them for users to configure if they want.