[agent-smith] introduce file detector

[kylos101]

Description

This'll warrant a new deployment for the workspace clusters, after updating the ops repo with the updated configuration.

Related Issue(s)

Fixes CLC-1701

How to test

instructions
a demo video

Documentation

Preview status

gitpod:summary

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[kylos101]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them. While these secrets were previously flagged, we no longer have a reference to the specific commits where they were detected. Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately. Find here more information about risks.

🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

It was a generated API token for the preview environment, and has been deleted, risk was limited to a non-prod ephemeral system, and is gone. 👋

[geropl]

One can clearly see the effort that went into this @kylos101 - impressive how you navigated the... existing "design"... in this place, and adapted in nicely made it work, without introducing breaking changes and working purely additive! Really great judgment here 💪 🚀

This makes this decision easy for me to approve, where although we don't want to invest into this software anymore, we can merge this with confidence and get exactly the relieve we were aiming for. 🎯

Code LGTM (ignore the nits, not relevant for this scope), tested and works! ✔️

[kylos101]

@geropl I fixed the metrics problem and asserted that our process infringements still work, too. I'll plan to land this on Monday.