fix: use RequestExecutor the Bearer AuthenticationManager

[Mohammad-Dwairi]

Situation

The current BearerAuthenticationManager expects a Transport in its constructor in order to use it for authentication requests. However, using a raw Transport makes the authentication requests to be executed outside the interceptors defined by the SDK, as these interceptors take place in the higher-level RequestExecutor.

By using the RequestExecutor instead of Transport in the BearerAuthenticationManager, all authentication requests will go through the same interceptors pipeline defined in the passed RequestExecutor.

Task

Modify the BearerAuthenticationManager to accept a RequestExecutor instead of Transport in its constructor, applying any needed changes along with this change.

Action

1. Updated the RequestExecutor to accept RequestExecutor instead of Transport.
2. Cleaned up the logging code in the BearerAuthenticationManager, Request/Response logging is now handled by the LoggingInterceptor even on the authentication requests.
3. Moved the logger instance to the LoggingInterceptor instead of injecting it from outside.

Testing

1. Manually Verified the results.
2. All existing tests are passing.

Results

Authentication requests made by the BearerAuthenticationManager are now going through the defined pipeline of interceptors defined by the SDK.