Fix: Patch all Critical/High CVEs from container scan (OS + app depen…

…dencies) (#17457)

* chore: update Python environment and dependencies in Dockerfile; upgrade nodemailer and typeorm in package.json

* chore: update dependencies in package.json

- upgraded esbuild from 0.27.0 to 0.28.1
- upgraded postcss from 8.4.24 to 8.5.18
- upgraded protobufjs from 7.2.3 to 7.6.5
- upgraded undici from 7.11.0 to 7.29.0
- added new dependencies:
  - @opentelemetry/core@^2.8.0
  - @grpc/grpc-js@^1.14.4
  - brace-expansion@^1.1.18
  - fast-uri@^3.1.5
  - multer@^2.2.0
  - nanoid@^3.3.17
  - socket.io-parser@^4.2.7
  - js-yaml@^4.3.1

* chore: enhance vulnerability CI workflow triggers and notifications

* Revert "chore: enhance vulnerability CI workflow triggers and notifications"

This reverts commit ff14653.

* chore: update nodemailer to version 9.0.5 and upgrade related dependencies

* chore: update nodemailer to version 9.0.5 and add @types/nodemailer

* chore: update fast-xml-parser to version 5.5.7 and adjust dependencies

* chore: update version to 3.20.210-lts across all components

---------

Co-authored-by: gsmithun4 <gsmithun4@gmail.com>

Fix: guard against null group/app names in Groups permissions UI (#17431

)

* fix: guard against null group/app names in GroupChipTD

Adding an app with no resolved name to a group's custom permissions
crashed the Groups permissions UI with a generic error screen —
renderGroupChip called .toLowerCase() on a null name with no guard.

Scoped to this defensive fix only; the backend flow that can produce
a null name here is changing separately and will address the root
cause differently.

* fix: skip apps with no resolved name in the addable-apps picker

An app/module/workflow with no resolved name (e.g. only present on a
non-default branch) rendered as an empty box in the group permissions
addable-apps picker. Filter these out instead of showing a blank entry.

Cleared with product: hiding these entries is an accepted interim
fix while the underlying branch-scoping behavior is addressed
separately on the backend.

* chore: update version to 3.21.59-beta

---------

Co-authored-by: gsmithun4 <gsmithun4@gmail.com>

chore: point ee submodules at lts-3.16 tips (#17459)

The gitlinks recorded on lts-3.16 pointed at fix/ai-bugs-3 merge commits
(frontend/ee e9bbcef9, server/ee c130897a) that are not reachable from the
submodules' lts-3.16 branches. The same changes landed properly on those
branches via ee-frontend#581 and ee-server#747.

Update the pointers to the current lts-3.16 tips so release tags land on
the release branches:

  frontend/ee  e9bbcef9 -> eea04224
  server/ee    c130897a -> 3a845efa

Merge pull request #17435 from ToolJet/fix/nav-nesting-resolution-main

Fix: Allow nesting component expression resolution [BETA]

Merge pull request #17423 from ToolJet/chore/update-ee-submodule-refs

chore: update ee submodule references to latest main

chore: update version to 3.20.208-lts across all components

Import CSV Tooljet DB (#17231)

* init

* await

* update delete

* app export

* type

* count

* null fix

* chore: update version to 3.20.207-lts across all components

---------

Co-authored-by: Midhun G S <gsmithun4@gmail.com>

Release v3.20.206-lts

Release v3.20.205-lts

Add workspace settings groups route and improve error handling in get…

…PrivateRoute (#17343)

* Add workspace settings groups route and improve error handling in getPrivateRoute

* Bump version to 3.21.56-beta across all components