Using Google Service Account Without Using JSON file

[denismatiu]

Issue Description:
Currently, there is a need for an alternative method to using Google Service Account without relying on JSON files. This becomes particularly convenient when hosting a project on Google Cloud, as it eliminates the additional challenge of managing JSON file rotation for the service account.

Proposal:
Implementing a solution that allows for the use of Google Service Account without the dependency on JSON files would greatly enhance the workflow for projects hosted on Google Cloud. This alternative method could simplify the authentication process and reduce the need for manual intervention in handling JSON file rotations.

Benefits:

Simplified Workflow: Users can seamlessly integrate Google Service Account without the overhead of managing JSON files.
Reduced Complexity: Eliminating the need for JSON file rotation streamlines the authentication process, reducing potential points of failure.
Improved Security: A more direct integration method may enhance security by reducing the exposure of sensitive credentials in JSON files.
Additional Context:
If the project is hosted on Google Cloud, this proposed enhancement would alleviate the burden of dealing with JSON file rotations, making the integration process more straightforward and user-friendly.

Note:
Consideration should be given to backward compatibility and the impact on existing implementations to ensure a smooth transition for users adopting this alternative approach.