fix(component): make client password and bearer strategy as mandatory

[sf-sahil-jassal]

make bearer strategy non optional, resulting client password strategy also not optional

GH-209

Description

Making the bearer strategy mandatory. But, by only making the bearer as manadatory, failed in test cases. Seems like, client password strategy is also needed for the same (infact all strategies as client is always needs to be authenticated first). So, I also made client password strategy as mandatory.

Fixes #209

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Intermediate change (work in progress)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [ ] Test A
• [ ] Test B

Checklist:

• [ ] Performed a self-review of my own code
• [x] npm test passes on your machine
• [x] New tests added or existing tests modified to cover all changes
• [ ] Code conforms with the style guide
• [ ] API Documentation in code was updated
• [ ] Any dependent changes have been merged and published in downstream modules

[sonarcloud[bot]]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[yeshamavani]

:tada: This PR is included in version 11.0.1 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: