feat: remove context category unit primitive checks

What does this merge request do and why?

This MR removes the unit primitive checks that are performed based on the categories of the additional context passed in a StartRequest.

The checks are controlled by a client request anyway and doesn't provide any security guarantees. We already exploit this behavior by passing any context for Web Agentic Chat as a repository category. They are also misleading as a developer may put some content in a specific category and have it rejected due to a missing unit primitive.

Currently, it causes the flows to fail with PERMISSION_DENIED error: https://cloudlogging.app.goo.gl/FnTHyHenJVXtAqQL7

Related discussion: https://gitlab.slack.com/archives/C09FJ94LHJA/p1762244959913179

Edited by Igor Drozdov

Merge request reports

Loading