Unsafe `as any` type assertion in CurrentChatTags component

Issue Description

The CurrentChatTags component in apps/meteor/client/views/omnichannel/additionalForms/CurrentChatTags.tsx uses an unsafe as any type assertion with a FIXME comment:

onChange={handler as any} // FIXME: any

Root Cause

The component defines its handler prop type as handler: (value: { label: string; value: string }[]) => void, but AutoCompleteTagsMultiple (which wraps PaginatedMultiSelectFiltered) expects onChange: (values: PaginatedMultiSelectOption[]) => void, where PaginatedMultiSelectOption = { value: string | number; label: string }.

The mismatch is value: string vs value: string | number, which caused the need for the unsafe as any cast.

Expected Behavior

The component should use PaginatedMultiSelectOption from @rocket.chat/fuselage directly, eliminating the type mismatch and removing the need for an unsafe cast.

Affected Files

• apps/meteor/client/views/omnichannel/additionalForms/CurrentChatTags.tsx
• apps/meteor/client/views/omnichannel/components/Tags.tsx (consumer)

Start with apps/meteor/client/views/omnichannel/additionalForms/CurrentChatTags.tsx and compare its handler prop with the PaginatedMultiSelectOption type from @rocket.chat/fuselage. Check apps/meteor/client/views/omnichannel/components/Tags.tsx for consumer compatibility. Done means the handler uses the shared option type, the as any assertion and FIXME are removed, and the TypeScript checks pass.