Worklog for task "Bug: projects should not be implicitly filtered by the current user"

Observation: The `projects(take: 100) { id name }` query returned an empty list when a current user was present. Hypothesis: the `projects` resolver implicitly accounts for the current user and returns only their projects. Expected behavior: The general `projects` query should not automatically restrict the selection to the current user's projects unless such a filter is explicitly passed in the arguments or provided by a separate operation/access policy. Actual behavior: When a current user is present, judging by the result, the selection is restricted to their projects, making the global list of projects inaccessible. Steps to reproduce: 1. Execute the GraphQL query: `query { projects(take: 100) { id name } }` in the context of an authorized user. 2. Compare the result with the expected global list of projects. 3. Check the `projects` resolver for implicit addition of a filter by the current user. Action required: Remove the implicit user filtering from `projects` or move the user-specific selection into a separate explicit filter/query, while preserving server-side access restrictions where they are actually needed.