Evaluate clone-db workflow for breaking the cache_table in both stable and staging

[dave-kennedy-ecs]

Current Behavior

Evaluate the clone-db workflow, which is breaking the cache_table in both stable and staging, when ran. When cache_table is broken, users are kicked out of their session.

May want to investigate flags that can be passed to cg-manage-rds (and/or pg_dump) to preserve cache_table in the source database.

Expected Behavior

When job is run, a user who has logged into stable before the job was started, will not be kicked from their current session and forced to log in again once the job has completed.

When job is run, a user who has logged into staging before the job was started, will not be kicked from their current session and forced to log in again once the job has completed.

Steps to Reproduce

1. Log into stable. Log into staging.
2. Run the clone-db workflow and wait until it completes.
3. Click a link in the stable interface and expect not to have to log in again. Same for staging.

Environment

Stable and staging

Additional Context

No response

Issue Links

No response