Don't allow users to chat with Concierge when blocked

[puneetlath]

Details

This PR makes a few changes/updates to the concierge blocking functionality.

1. It fixes the bug where we weren't actually blocking the user from chatting with Concierge. This is because we weren't asking for the isBlockedFromConcierge NVP in the API call. This was broken at some point.
2. Makes it so that if a user does chat with Concierge while blocked, we handle the API response. This is possible because we only get the user details every 30 min. So if a user is in active conversation with Concierge and is blocked, they can still seemingly be able to keep chatting until the user details refresh. This PR catches that API response, throws a growl, and prevents them from sending further messages.
3. Updates the style on the compose box so that it won't appear selected when the user is blocked from using it.

Screen.Recording.2022-01-20.at.5.30.18.PM.mov

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/172842

Tests

• Verify that no errors appear in the JS console

1. sign into an account on new dot and go to your concierge chat
2. send a message to concierge
3. open expensify.com.dev/concierge/
4. sign in with an @expensify.com email address
5. click Tools
6. use the find chats by user tool to find the chat with your user
7. click "user info"
8. block your user
9. go back to new dot and try to chat with concierge again
10. verify that you see the growl that you are barred from chatting
11. verify that your message that you just sent is removed from the chat history
12. verify that the input is disabled and you are no longer able to message concierge
13. verify that the blue highlight is no longer shown around the input

QA Steps

• Verify that no errors appear in the JS console

Will need to be tested by an Expensify employee on production. Steps are the same as above.

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

Screenshots

Web

Video above.

Mobile Web

Desktop

iOS

Android

[chiragsalian]

Changes LGTM and code works well.

[MelvinBot]

Triggered auto assignment to @Beamanator (InternalQA), see https://stackoverflow.com/c/expensify/questions/5042 for more details.

[botify]

@chiragsalian looks like this was merged without passing tests. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[chiragsalian]

I think perhaps the internalQA label might have screwed up some stuff since i don't think we've used it before for App repo. Either way it's all good melvin and botify.

[OSBotify]

🚀 Deployed to staging by @chiragsalian in version: 1.1.32-1 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[OSBotify]

🚀 Deployed to production by @roryabraham in version: 1.1.33-3 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅