feat: [sc-38531] Admin: Implement Organizations management UI

[Cwagne17]

This pull request introduces the new Organizations feature to the admin module, including navigation, routing, and UI components, as well as updates to the organization entity model and related imports. The main changes involve adding the Organizations admin page, updating the Angular module and routing configuration, refactoring the organization entity, and cleaning up imports throughout the codebase.

Organizations Admin Feature:

• Added the OrganizationsComponent and its unit tests, providing UI and logic for managing organizations in the admin area.
• Updated the sidebar (sidebar.component.html) to include a navigation link to the new Organizations page, visible to admins and editors.
• Registered the new Organizations route in admin.routing.ts and included the component in the admin module declarations and imports. [1] [2] [3]

Entity Model Updates:

• Replaced the old organization.ts interface with a more comprehensive Organization model in organization/organization.ts, including fields for sector, levels, verification, and more. [1] [2]
• Updated the main entity barrel (entity/index.ts) to export the new organization types and refactored imports in multiple files to use the new structure. [1] [2] [3] [4]

Code Cleanup and Refactoring:

• Cleaned up and reorganized imports in several files for consistency and to reflect the new organization entity structure. [1] [2] [3] [4]
• Updated Angular module imports and declarations in admin.module.ts to ensure all new components and Angular Material modules are included and properly ordered. [1] [2]Story details: https://app.shortcut.com/clarkcan/story/38531

Screen.Recording.2026-01-09.at.2.56.27.PM.mov

[dsoto18]

pretty cool not sure if I've seen we have any tests like this anywhere else on our clients

[curlyLasagna]

it's autogenerated when creating a new angular component via ng generate component.

Historically, these spec files are left alone

[dsoto18]

I wonder if its possible to have builder io use our clark-admin-pagination component, since we already have that built in. Also could help reduce the amount of new imports we have to materials too. It did do a decent job of using our other components like the clark-popup

[dsoto18]

Really long css file, but to my eyes it looks good. Made sure it was using our global variables from the vars scss file which for the most part looks like it is

[dsoto18]

Looks pretty good to me with just a few comments, I know this would be one of the last things to go out as part of the epic so should we just keep this PR up and the story in code review in the meantime? And should we wait until later to remove all the mock data in the component.ts file