feat: add dataflow to code issue data [IDE-134]

[bastiandoetsch]

Pull Request Submission

Please check the boxes once done.

The pull request must:

• Reviewer Documentation
  • follow CONTRIBUTING rules
  • be accompanied by a detailed description of the changes
  • contain a risk assessment of the change (Low | Medium | High) with regards to breaking existing functionality. A change e.g. of an underlying language plugin can completely break the functionality for that language, but appearing as only a version change in the dependencies.
  • highlight breaking API if applicable
  • contain a link to the automatic tests that cover the updated functionality.
  • contain testing instructions in case that the reviewer wants to manual verify as well, to add to the manual testing done by the author.
  • link to the link to the PR for the User-facing documentation
• User facing Documentation
  • update any relevant documentation in gitbook by submitting a gitbook PR, and including the PR link here
  • ensure that the message of the final single commit is descriptive and prefixed with either feat: or fix: , others might be used in rare occasions as well, if there is no need to document the changes in the release notes. The changes or fixes should be described in detail in the commit message for the changelog & release notes.
• Testing
  • Changes, removals and additions to functionality must be covered by acceptance / integration tests or smoke tests - either already existing ones, or new ones, created by the author of the PR.

What does this PR do?

This updates Language Server to the latest version, which includes snyk/snyk-ls#449. This enables the IDEs to display a correct dataflow, and it is needed to feed the IntelliJ Snyk Code integration of LS. This also integrates the latest Go Application Framework (snyk/go-application-framework@d58d5f3), which only brings CODEOWNER and linter changes.

Risk: LOW

Where should the reviewer start?

snyk/snyk-ls#449

How should this be manually tested?

Build the CLI with this change, then configure the build directory in IntelliJ, using the latest IntelliJ code from snyk/snyk-intellij-plugin#474. Then switch the feature flag in the IntelliJ Registry and test whether the dataflow populates like before.

Any background context you want to provide?

What are the relevant tickets?

IDE-134

Screenshots

Additional questions