fix: joinCall set correct mute state based on microphoneOn parameter

[bfwg]

What

Fixed a bug where the initial muted state is not being set correctly.

Why

When microphoneOn is true, muted will be true which is backward of what the code is intended to do.

How Tested

I tested calling joinCall with microphoneOn parameter true and the call will start muted which is incorrect.

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?

• This change causes current functionality to break.

[prprabhu-ms]

Thank you for your contribution!

I checked in the rest of the codebase and turns out we don't ever call joinCall with microphoneOn set (to either true or false). That is why things were not on fire already.

Thanks for catching this.

[prprabhu-ms]

microphoneOn is optional. If we check for falsiness, calling joinCall() without any arguments will cause muted to be set to true.

So, fallback on undefined, and then check for falsiness...

Suggested change

	const audioOptions: AudioOptions = { muted: !microphoneOn ?? !this.getState().isLocalPreviewMicrophoneEnabled };
	const audioOptions: AudioOptions = { muted: !(microphoneOn ?? this.getState().isLocalPreviewMicrophoneEnabled) };

[bfwg]

Great suggestion. I've fixed my code.

[prprabhu-ms]

Do you mind running rush changelog and providing a changelog for this PR?

The type should be "patch" (as this is a bugfix). The PR title is a good change description.

[prprabhu-ms]

I'm trying to figure out why chromatic is unhappy.

[ghost]

All CLA requirements met.

[bfwg]

Done.