Add google_backup_credentials table to database schema - #53

• Introduced a new table google_backup_credentials to store Google OAuth tokens, including fields for user ID, email, access tokens, and timestamps for creation and updates.
• Created unique and standard indexes for efficient querying on user ID and email.
• Updated migration scripts and database schema files to reflect these changes across different database systems (PostgreSQL, CockroachDB, Spanner).
• Enhanced the overall database structure to support better management of Google OAuth credentials for users.

What:

Why:

Please describe the tests:

• Test 1:
• Test 2:

Please describe the performance impact:

Code Review Checklist (to be filled out by reviewer)

• NEW: Are there any Satellite database migrations? Are they forwards and backwards compatible?
• Does the PR describe what changes are being made?
• Does the PR describe why the changes are being made?
• Does the code follow our style guide?
• Does the code follow our testing guide?
• Is the PR appropriately sized? (If it could be broken into smaller PRs it should be)
• Does the new code have enough tests? (every PR should have tests or justification otherwise. Bug-fix PRs especially)
• Does the new code have enough documentation that answers "how do I use it?" and "what does it do?"? (both source documentation and higher level, diagrams?)
• Does any documentation need updating?
• Do the database access patterns make sense?