Add Themis updates to changelog

[gilfaizon]

Overview

This details the changes in the latest version of Themis, so we can release a new version of the CLI.

Acceptance criteria

Users will be able to CLI-side license scan the most recent additions to themis.

Testing plan

No explicit testing was done, the latest themis version will be pulled automatically.

Risks

This is my first time cutting a release

References

Themis PR with context:

• https://github.com/fossas/themis/pull/75

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.

[spatten]

Looks great!

Can you also add a link to the PR for your other change?

- Adds clarity to "Invalid project permission" error message, instructing user to specify a team using `fossa analyze --team` or in the `.fossa.yml` file. ([#1476](https://github.com/fossas/fossa-cli/pull/1476))