fix: correct chatAdapterOptions handling inside useAzureCommunicationChatAdapter

[neilcampbell]

What

Forward chatAdapterOptions from the useAzureCommunicationChatAdapter hook args to the underlying createAzureCommunicationChatAdapter call.

Why

chatAdapterOptions is destructured from the hook's args parameter but is never passed through when creating the adapter. This means any options provided by the caller (e.g., custom topic fetching behaviour) are silently ignored.

How Tested

• Existing unit tests pass (AzureCommunicationChatAdapter.test.ts and all other test suites).
• Ran rush build, rush lint, and rush test successfully.

Process & policy checklist

• I have updated the project documentation to reflect my changes if necessary.
• I have read the CONTRIBUTING documentation.

Is this a breaking change?
No

[neilcampbell]

@microsoft-github-policy-service agree