v0.3.0: Add Cloudflare Access headers support for Metabase API requests (#12)

# Description 
Add support for Cloudflare Access headers to bypass application
protection when accessing Metabase APIs.

## Background

Some organizations deploy Metabase behind Cloudflare Access for
additional security protection. Cloudflare Access requires specific
client headers (`CF-Access-Client-Id` and `CF-Access-Client-Secret`) to
authenticate and bypass the access control checks.

Without these headers, requests to protected Metabase instances will be
blocked by Cloudflare Access, preventing the sync worker from accessing
the Metabase API endpoints.

# Changes

- Added support for CF_ACCESS_CLIENT_ID and CF_ACCESS_CLIENT_SECRET
environment variables
- Modified all Metabase API requests to conditionally include Cloudflare
Access headers when the environment variables are provided
- Updated function signatures to pass the CF Access credentials through
the call chain
- Headers are only added when environment variables are set, ensuring
backward compatibility

 # Usage

Set the following environment variables when running the worker against
a Cloudflare Access-protected Metabase instance:
  CF_ACCESS_CLIENT_ID=your_client_id
  CF_ACCESS_CLIENT_SECRET=your_client_secret

v0.2.0

Build for both amd64 and arm64

v0.1.0

Implement FREQUENCY

v0.0.1

ENG-0 - Add github action that push into an ECR repo automatically (#5)