include projectId in --json output

[spatten]

Overview

Delivers ANE-2002

When you run fossa analyze --json, we want to also include the full project ID in the output. the project ID is typically just the existing project field with custom+ prepended to it:

fossa analyze --json
{
  "branch": null,
  "id": "custom+24987/ane-1993-missing-preview$2024-08-29T21:53:33Z",
  "project": "24987/ane-1993-missing-preview",
  "projectId": "custom+24987/ane-1993-missing-preview",
  "revision": "2024-08-29T21:53:33Z",
  "url": "https://app.fossa.com/projects/custom%2b24987%2fane-1993-missing-preview/refs/branch/master/2024-08-29T21:53:33Z"
}

Acceptance criteria

When you run fossa analyze --json we include the full projectId in the output

Testing plan

Run fossa analyze --json on a project and take a look at the output

Risks

This is low risk

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