Remove project routing from the user dashboard

[Ma77Ball]

Task Summary

This task is to remove project routing and the related now-dead code:

• Remove the project routing test case in frontend/src/app/dashboard/component/user/list-item/list-item.component.spec.ts (lines 145–149) that asserts project entries route to [USER_PROJECT, "200"].
• Remove the corresponding project-routing logic in list-item.component.ts (the initializeEntry / entryLink handling for type: "project").
• Remove the user/project and user/project/:pid route definitions from routing.module.ts, along with any now-unused component references (UserProjectComponent, UserProjectSectionComponent).
• Clean up any other now-orphaned imports or references to those routes/components.

Task Type

• Refactor / Cleanup
• DevOps / Deployment / CI
• Testing / QA
• Documentation
• Performance
• Other

[Ma77Ball]

/take

[Yicong-Huang]

Did we decide to remove project yet?

cc @apache/texera-committers

[aglinxinyuan]

It's removed.

[Yicong-Huang]

It's removed.

is it deprecated or removed? can you help me locate the related issue/PRs as I could not find them...

[aglinxinyuan]

It's removed.

is it deprecated or removed? can you help me locate the related issue/PRs as I could not find them...

I was wrong. It's deprecated instead of removed. It's hidden by default on the frontend, but related code is still in the codebase.

[Yicong-Huang]

thanks. So it is deprecated. I think we should

1. hide by default on frontend
2. disable frontend routing by default,
3. disable backend endpoints by default.

I don't know if we want to remove the codebase yet... I am not saying we should not remove it, just hope we can discuss before doing so. @Ma77Ball can we hold of on the removal for now?

[Ma77Ball]

Yes, I will hold off. Should I remove the issue or keep it for later?