S3 credentials are cached too long Admin settings | Osmesa

### To reproduce:

- Browse to the staging environment,
- Browse to a user's profile page, and verify the Extent of Edits map is displaying .mvt tiles
- Sign in to scoreboard as admin.
- Go to Admin menu | Edit app settings
- Safely copy/save the OSMesa S3 AWS secret
- Edit the OSMesa S3 AWS secret to some other string
- Submit to save
- Now reload the app in your browser, and you will see the User Extent of Edits map will continue to successfully load tiles from s3, even though we have invalidated the aws credentials.
- reminder: revert the AWS secret string to what it was.

### Expected

- If aws credentials are invalidated or changed, they should take effect immediately, or after some short interval. Either the settings controller should flush the cache when settings are saved, or settings could be refreshed in the `npm run clocks` script.

### Workaround

- ssh to the staging environment and run `sudo systemctl restart scoreboard-api`
- reload the scoreboard app in your browser, and you should see now when you browse to a user's profile page, and verify the Extent of Edits map is NOT displaying .mvt tiles.

Relates to #595