fix: explicitly check the type of `Accounts_AllowUserStatusMessageChange`

Proposed changes

allowUserStatusMessageChange can be true, false or undefined We should only disable status change if it is explicitly false.

Issue(s)

How to test or reproduce

Enable or disable the setting and see if the status change menu is visible or not. Also check on a server that has not changed this setting (which must have the value of undefined), to see if the option exists or not.

Screenshots

Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves a current function)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update (if none of the other choices apply)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if applicable)
[ ] I have added necessary documentation (if applicable)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments

Jira: SUP-536

RocketChat / Rocket.Chat.ReactNative

fix: explicitly check the type of `Accounts_AllowUserStatusMessageChange` #5642