Build electron package using Bazel

[farmaazon]

Current progress:

• esbuild configuration for building electron client
• Removing Project Manager Remove project manager #14174
  • Remove project manager from the codebase, simplifying packaging
• Electron Builder Configuration for multiplatform package build
  • Mac
    • Basic unpackaged build
    • Do we really need rules_js patchfs flag to avoid sandboxing issues?
    • Signing and notarization
    • DMG packaging
    • Support building dmg with hdiutil
      • Experiment with providing hdiutil via toolchain or repository (turns out the issue is happening in hdiutil’s business logic)
      • Investigate hdiutil sandboxing issues by debugging
      • Consider HFS+ vs APFS images (https://github.com/create-dmg/create-dmg)
      • Use out-of-sandbox build step or fix the issue
  • Windows
    • Fix engine issues (see below)
    • Do we really need rules_js patchfs flag to avoid sandboxing issues? Yes we do.
    • Build!
    • Integrating installer/uninstaller (or simplifying this part of distribution)
  • Linux
    • AppImage build
    • --no-sandbox fix
    • Mysterious failure to locate java when using JVM build of the engine
    • Fix application icon in AppImage Missing icon in standalone Enso #6480
  • Bring back file associations
  • Proper version info configuration
    • Version info in Electron
    • Version info in GUI
    • Version info in Engine
    • Version info in package metadata (electron-builder-config.cjs must contain correct version info)
    • Mirror or simplify release version generation in the Rust build script
  • Engine distribution files are incorrectly symlinked, not copied to the final package
  • Configuration in TypeScript (?, it causes issues, might not worth it)
  • Update electron-builder to the latest version
    • Fix build
  • Provide new .icon on Mac Add icon for MacOS Tahoe #14118
  • Replace JVM engine build with native build when it’s ready
• Backend build
  • JVM engine distribution
    • Linux
    • Mac
    • Windows
      • JNI build for parser produces multiple artifacts while a single one is expected (patch included in Build electron package on Linux with Bazel #14181)
      • Support PATH and other environment variables in a cross-platform way
  • Native engine distribution Build native image with Bazel #14105
    • Mac
    • Linux (untested)
    • Windows (untested)
    • CI
  • SmallJDK build (thanks @Akirathan, included in Build electron package on Linux with Bazel #14181)
  • THIRD-PARTY license information packaging
  • Fix missing data directories in engine distribution
  • Simplify directory structure to simplify path management in build configuration (?, e.g., no version and platform in paths)
• Simplifying electron client
  • Prune ide-desktop package #14069
  • Reconfigure CI runners to use more shared memory—it helps with package tests stability Prune ide-desktop package #14069
  • Remove remaining Chromium flags Prune ide-desktop package #14069
  • Fix logger issues Logging non-serializable objects throws an error #14121 (patch available, untested)
• Do we implement our custom toolchains correctly? It seems repositories are formed with files for all supported platforms (e.g., Win, Mac, and Linux flatc distributions on Win)
• CI
  • Gather statistics (like build time) to track improvements
  • Basic smoke test for testing app packaging on Linux
  • …

[farmaazon]

• Use bazel to get engine dependencies (graalVM, ...)
  • flatc may be skipped - just comment-out the step in build.sbt.
• update CI for packaging too (integration test may be still a step of packaging job).
• remove redundant CI jobs.