fix audit remove script and modify GHA workflow

[craigrva]

Resolves APPEALS-26130

Modifies our Github Actions config as described below

Excludes 'db/scripts' in .codeclimate.yml

Description

Add a rescue block to script remove_caseflow_audit_schema.rb to prevent it from erroring and causing failures when attempting to run make reset after initially creating docker containers/volumes

Modify .github/workflow.yml caseflow_rspec_job to:

• Set yarn's cache directory to a specified value, so that path resolves correctly with later steps
• Changed the paths cached to include the yarn cache (set above) and the node_modules
• Modified the cache's key value to be based on the yarn.lock file so that changing dependencies will generate a new cache

These changes will properly cache the frontend dependencies in a similar way to how we cache the backend dependencies for CI runs. It will save a significant amount of time each run and help minimize the chance that problems with external dependency repositories can cause our builds to fail.

Acceptance Criteria

• Code compiles correctly
• Rspec test nodes build without error and run tests
• make reset (or similar commands) can be run without the database caseflow_certification_development in the postgres server

Testing Plan

WARNING: This test plan will drop your database and then re-seed it

1. Run bundle exec rake db:drop
2. Run make audit-remove and verify that you see the console output "Database caseflow_certification_development does not exist; skipping make audit-remove"
3. Run make reset
4. Verify that make reset runs without erroring due to ActiveRecord::NoDatabaseError

Additional post-merge instructions

Manually trigger the Rspec Jest Lint workflow in Github Actions for the master branch. This should generate the master branch yarn cache

Best practices

Code Documentation Updates

• Add or update code comments at the top of the class, module, and/or component.

Code Climate

Your code does not add any new code climate offenses? If so why?

• No new code climate issues added

Monitoring, Logging, Auditing, Error, and Exception Handling Checklist

Error Handling

• Are errors being caught and handled gracefully?
• Are appropriate error messages being displayed to users?
• Are critical errors being reported to an error tracking system (e.g., Sentry, ELK)?
• Are unhandled exceptions being caught at the application level ?

[codeclimate]

Code Climate has analyzed commit a5ae986 and detected 0 issues on this pull request.

View more on Code Climate.