[FSSDK-8184] override attribute bug fix of track method

[junaed-optimizely]

Summary

While checking the second parameter of OptimizelyReactClient.track, to decide if its a userId or eventTags, overrideAttributes is set to undefined if the second argument is eventTags, which should not be the case. userId and attribute overrides are two seperate things.

Test plan

• Test structure of track method of React client has improved
• New test case added to cover this specific scenario

Issues

• FSSDK-8184

[github-actions]

Jest Coverage Report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	98.95% (-0% 🔻)	846/855
🟢	Branches	91.6%	338/369
🟢	Functions	97.52%	157/161
🟢	Lines	99.09% (-0% 🔻)	764/771

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	client.ts	99.27% (-0% 🔻)	94.33%	96.97%	99.5% (-0% 🔻)

Test suite run success

263 tests passing in 10 suites.

Report generated by 🧪jest coverage report action from 99c53b9

[mikechu-optimizely]

LGTM.

Do need to cover if track's overrideUserId is null or if _client is not initialized / null? Maybe overkill?