feat(core): Update endpoint to retrieve folder to allow returning the path to root (no-changelog)

[RicardoE105]

Summary

This PR enhances the folder retrieval endpoint to return the path from a folder to the root, allowing clients to display breadcrumb navigation or full folder paths in the UI.

Technical Details

1. The implementation uses a Common Table Expression (CTE) with a recursive query to efficiently calculate the path from any folder to the root
2. The path is returned as an array of folder names, starting with the root folder and ending with the requested folder
3. The method only performs the additional path calculation when the path field is explicitly requested in the select parameter, maintaining backward compatibility

Related Linear tickets, Github issues, and Community forum posts

https://linear.app/n8n/issue/ADO-3546/add-path-to-folders-returned-from-endpoint

Review / Merge checklist

• PR title and summary are descriptive. (conventions)
• Docs updated or follow-up ticket created.
• Tests included.
• PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

[codecov]

Codecov Report

Attention: Patch coverage is 32.25806% with 21 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...ages/@n8n/db/src/repositories/folder.repository.ts	0.00%	21 Missing ⚠️

📢 Thoughts on this report? Let us know!

[cubic-dev-ai]

mrge found 1 issue across 6 files. Review it in mrge.io

[Cadiac]

I pushed a suggestion of how we could do this instead to branch https://github.com/n8n-io/n8n/tree/ado-3546-add-path-to-folders-returned-from-endpoint-simplified, lets talk about this today when you're online?

[Cadiac]

These casts seem fishy and unnecessary 🤔

[Cadiac]

Can we avoid changing these to optional? They should still be present always if folder is of this type

[Cadiac]

I'm suggesting we simplify this, instead of introducing the new type can we change this type to

export type FolderWithWorkflowAndSubFolderCount = Folder & {
	workflowCount: boolean;
	subFolderCount: number;
	path?: string[];
};

and then enrich the path only if the select option is used, otherwise just leaving it out? This allows us to keep the FolderRepository typed as

export class FolderRepository extends Repository<FolderWithWorkflowAndSubFolderCount> {

and removes the need for casts

[RicardoE105]

The reason I did not want the repository to take FolderWithWorkflowAndSubFolderCount it's because does not have those values in the entity. So if you in this repo do: this.create, it looks like you can pass the fields in FolderWithWorkflowAndSubFolderCount and that is not correct. The same with update. Those fields are only included if the getMany method and the select parameter explicitly include them. Thoughts?

[Cadiac]

Show must go on, lets refactor the repository types later 👍

[github-actions]

✅ All Cypress E2E specs passed

[janober]

Got released with n8n@1.94.0