Hide statuses, custom fields and iterations for user namespaces

What does this MR do and why?

Configurable statuses, custom fields, and iterations are only supported for ultimate and premium plans within group and project namespaces.

Since these features are not available for user namespaces, this MR ensures they are properly hidden and inaccessible in that context.

This fix is based on @engwan suggestion to update the license checks to account for personal namespaces. It also reverts a previous attempt to address a similar issue implemented in !192610 (merged).

References

• #556994 (closed)

Screenshots or screen recordings

Before	After

How to set up and validate locally

1. Create a new issue board under your personal namespace.
2. Try to create a new list on the board and confirm that the Status and Iteration options are no longer available as list types.
3. Attempt to filter issues on the board and verify that Status and Iteration filters are no longer shown.
4. Open an issue from the board and confirm that the Status, Iteration, and Custom field widgets are not visible.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.