Issue:
fix(user): use mget to check in blocklist

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
Use MGet to check whether role or user is blacklisted in KV. Instead of checking user and role separately, MGet can help to do it in one call.


### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
Enhancement

## How did you test it?
Singup --> Sigin --> Create a new role --> Invite new user with newly created role --> Sign In new user --> perform some operations which the user with assigned role can perform --> now update the role --> try performing same operation for the newly invited user. It won't be valid since role has been blocklist.
Can also check KV for blocklisted role_id and user_id.

Curls for singup/singin

curl --location 'http://localhost:8080/user/signup' \
--header 'Content-Type: application/json' \
--header 'Cookie: token=JWT' \
--data-raw '{
    "email": "test121@juspay.in",
    "password": "Test@12",
    "country": "IN"
}
'
curl --location 'http://localhost:8080/user/signin' \
--header 'Content-Type: application/json' \
--header 'Cookie: token=JWT' \
--data-raw '{
    "email": "test12345@juspay.in",
    "password": "260e5c5c-dc96-4cb9-870c-eb18ab8ab577"

}'
Create Role:

curl --location 'http://localhost:8080/user/role' \
--header 'Authorization: Bearer JWT' \
--header 'Content-Type: application/json' \
--data '{
  "role_name": "test",
  "groups": ["operations_view", "operations_manage"],
  "role_scope": "organization"
}'
Update Role:

curl --location --request PUT 'http://localhost:8080/user/role/role_QvY913dYo2b05D64bJ8l' \
--header 'Authorization: Bearer JWT' \
--header 'Content-Type: application/json' \
--data '{

  "groups": ["operations_view"]

}'

## Checklist
<!-- Put an `x` in the boxes that apply -->

- [x] I formatted the code `cargo +nightly fmt --all`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
- [ ] I added a [CHANGELOG](/CHANGELOG.md) entry if applicable


Resolution:
<think>
PR Context:
- Title: fix(redis_interface): remove mget function from redis interface
- Merged: 2024-04-05T12:22:15Z
- Files changed: 1 files
- Commits: 2 commits

Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
Getting multiple values from Redis at one time was working fine in local environment but was failing when deployed because  of mutiple clusters at infra level.

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This 
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** fix(redis_interface): remove mget function from redis interface (#4303)
Co-authored-by: hyperswitch-
Files to modify:


**crates/redis_interface/src/commands.rs**
  Remove:
    - function: pub::get_multiple_keys
    - function: pub::get_and_deserialize_multiple_keys