Edit Content: Create Guard to handle redirect between new and old version

Summary

Right now in our codebase, we have to manually check all the time if we are able to navigate to the new Edit Content Screen, leading to duplicated logic, fetchs and code.

We should use the already existing editContentGuard for this behavior.

And remove all calls of dotContentTypeService that leads to a redirect due to lack or presence of permissions for accessing the new Edit Content.

An ideal solution would be to not do any call at all and have this information locally.

Acceptance Criteria

• We should centralize the logic to check if a Content Type or Content is able to enter the new portlet at route level
• Double check all instances of dotContentTypeService to prevent more calls to do redirects
• Be sure that the new logic covers all edge cases covered by the already existing code

dotCMS Version

trunk_latest

Proposed Objective

User Experience

Proposed Priority

Priority 3 - Average

Start with core-web/apps/dotcms-ui/src/app/api/services/guards/edit-content.guard.ts to understand the existing guard, then search the core-web codebase for dotContentTypeService calls that trigger redirects. Centralize the route-level checks and verify that all existing permission and content-type edge cases remain covered without redundant calls.