[Flow202][native][skip-ci] [57/x] Avoid looking up nullable type in non-nullable Set in ChatRouter
Summary:
Flow doesn't like that we're calling Set<string>.has with a ?string. To avoid this, I check the type before calling has() here.
NOTE: CI will fail on this diff. I considered the possibility of fixing Flow errors BEFORE upgrading Flow, but it wasn't possible... in some cases, the fixes to support the new version of Flow caused errors in the old version. I could have hidden these type errors with $FlowFixMe lines and then later revert those, but that seemed like too much busy work.
Depends on D10040
Test Plan: Confirm the Flow errors go away
Reviewers: tomek
Reviewed By: tomek
Differential Revision: https://phab.comm.dev/D10041