Update manual dependencies docs

[spatten]

Overview

closes #1027

• fix some discrepancies between the documentation for manual-deps and the schema
• fix a trailing comma in the schema for fossa-deps.yml
• Add a lint-check for the schemas
• Fix a miss-spelling of "fontawesome"
• Change spectrometer => fossa-cli in a few spots

Acceptance criteria

• the fossa-deps.yml schema should be valid
• invalid schemas should fail the lint-check
• we should use fossa-cli instead of spectrometer in our example URLs where possible
• The fetchers in the manual-dependencies documentation should match those in the schema

Testing plan

I tested that the linter caught an invalid schema by reverting the fix to the schema and checking that the linter failed.

Everything else is a documentation fix.

Risks

None

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

[zlav]

LGTM!

[zlav]

You should add the PR link to the end of the line.

[zlav]

🙌

[thernstig]

@spatten did this miss to fix bullet point 2) in #1027 ?

[spatten]

@spatten did this miss to fix bullet point 2) in #1027 ?

I think that there were two discrepancies: swift was not mentioned in the docs, and bower was not included in the schema. I updated both of these in the PR.

I think that fixes the problem. I've just looked again, and I think the two lists match. Did I miss something?

[thernstig]

@spatten you are correct, it was fixed properly, sorry for the noise.

[spatten]

@spatten you are correct, it was fixed properly, sorry for the noise.

No problem at all! Thanks for flagging this in the Issue :)