chore(benchmark): replace request with axios

[raymondfeng]

Replacing request with axios

Checklist

👉 Read and sign the CLA (Contributor License Agreement) 👈

• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• API Documentation in code was updated
• Documentation in /docs/site was updated
• Affected artifact templates in packages/cli were updated
• Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

[emonddr]

I like axios, nice!

[bajtos]

In #2672, I raised the following concern:

Many request alternatives are replacing errors reported by Node.js core with its own error classes, which makes troubleshooting extremely difficult.

That was in May 2019. What's the current status of Axios implementation, does it preserve low-level error details?

Ideally, I'd like us to use the same library across the entire loopback-next codebase, including connectors like REST and SOAP.

[raymondfeng]

Many request alternatives are replacing errors reported by Node.js core with its own error classes, which makes troubleshooting extremely difficult.
That was in May 2019. What's the current status of Axios implementation, does it preserve low-level error details?

I found a way to allow lower-level errors to be reported by providing a validateStatus function in the config. But this feature is not needed for benchmark testing.

Ideally, I'd like us to use the same library across the entire loopback-next codebase, including connectors like REST and SOAP.

Since this PR focuses on benchmark testing which is an internal module. I think axios does it job perfectly here. For connecting to other http services, I agree we can have a common http-client package.

[raymondfeng]

See #4637 as a follow-up PR.