Upgrade deprecated request-promise-native library

[palisadoes]

Describe the bug
When the command npm install --legacy-peer-deps is run for the first time as part of the installation process, this error message is seen.

npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142

To Reproduce

• See above

Expected behavior

1. No error message because the library has been updated, or suitably replaced, not because the error message has been suppressed.
2. All tests pass and are updated for the new library
3. If the package is no longer used, then it must be removed
4. No application functionality is affected

Actual behavior

• See above

Screenshots

• N/A

Additional details

• N/A

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359

[palisadoes]

@hharshas You have requested to be assigned to 10 issues in the space of 5 minutes. Everyone needs to get a chance to work on issues. Once you have been assigned two issues, the next person in line in the remaining 8 will be provided access. Please watch this video for guidance

• https://www.youtube.com/watch?v=3mjap16GYiY

Your actions are not in keeping with the spirit of the community. Please adjust your activities to be more collaborative.

@Cioppolo14 @noman2002 @Kevoniat please take note.

[hharshas]

@palisadoes would keep that in mind from now onwards

[sarthak17jain]

I would love to work on this

[Cioppolo14]

@sarthak17jain Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cioppolo14]

@sarthak17jain Are you working on this?

[varunsh17]

Would like to work upon the issue.

[Cioppolo14]

Unassigning due to inactivity.

[varunsh17]

These are the dependencies request-promise-native depends and are being used currently.
After uninstalling it, I see no difference (The talawa-admin localhost works fine).
I wanna ask Why are we not removing this dependency ?

[palisadoes]

Please read the issue's requirements

[varunsh17]

The Below mentioned lines indicate that request-promise-native library is still in use as it is indirectly use by other dependencies, our error is coming because of this. @palisadoes @Cioppolo14

Link1
Link2
Link3
Link4

[varunsh17]

@palisadoes @Cioppolo14
Should I consider removing those sub-dependencies too ? as I commented above that request-promise-native is still used by another packages internally..

[palisadoes]

Upgrade dependencies to the best of your ability by only editing the package.json file

[git-init-priyanshu]

I think we can close this issue now because the request-promise-native and left-pad libraries are both dependencies of the jest-enzyme library and my PR, #1501, removes the jest-enzyme library, thereby resolving both warnings.


After removing jest-enzyme library: