Refine GEAR's use of the Google API to be repeatable for other data tables and easily called in an auditable way

[hatfieldjm4]

The use of the Google API should be able to be called in a way that we know in the GEAR logs who initiated the Google API. Only those who have write permission in Google Manager (i.e. are listed in GEAR's acl database) should be able to call the Google API to add data to GEAR's database.

Calling this API should be easy to do if the user has the correct access rights. The use of this API, currently only writing data to the zk_systems_subsystems_records table, should be made so that it can be repeated for other tables in the database using another Google Sheet.

[isaiahsayalee]

The updates for this change have been pushed to the googleapi branch.

Completed updates:

• Google API functionality to authenticate and access a given sheet.
• Process to pull the zk_systems_subsystems_records from sheet and update db table.
• Nightly Cron Job to automatically run the updates.
  • Currently set to run M-F @ 2pm.
• Button added to Records-Management page to manually run the updates.
  • This new button is behind GEAR Manager.
  • Once clicked, the process will start and a loading animation will appear.
  • Once completed, a summary notification will display.
  • If errors, then a error notification will display.
• New logging features added to GEAR3.
  • Added logging when logging in as GEAR Manager.
  • Added logging when Google API is called.

Pending updates:

• Setting up a Google service account to generate token to access a Google sheet.
  • Embed Google API Token to .env file.