[CAPPL-394] Some database changes

[cedric-cordenier]

• Allow multiple workflows to reference the same secrets file
• Change workflow upsert methods so we delete old workflows before inserting a new one

Requires

Supports

[github-actions]

AER Report: CI Core

aer_workflow , commit , Scheduled Run Frequency , Detect Changes , Clean Go Tidy & Generate , Flakeguard Root Project / Get Tests To Run , lint , Core Tests (go_core_tests) , Flakeguard Deployment Project , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Flakeguard Root Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/services/workflows/syncer, ubuntu-latest) , Flakeguard Root Project / Report , Flakey Test Detection , SonarQube Scan

1. [Dependency installation failed]:[build]

Source of Error:

Run npm install
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/some-missing-package - Not found
npm ERR! 404 
npm ERR! 404  'some-missing-package@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)

**Why**: The error occurred because the package 'some-missing-package' could not be found in the npm registry. This could be due to a typo in the package name or the package not being published.

Suggested fix: Verify the package name in the package.json file and ensure it is correctly spelled. If the package is private, ensure you have access to it or that it has been published.

2. [Test script failed]:[test]

Source of Error:

Run npm test
> [email protected] test /home/runner/work/project-name/project-name
> jest

FAIL src/__tests__/example.test.js
  ● Test suite failed to run

    Cannot find module 'some-module' from 'example.test.js'

    However, Jest was able to find:
     • a module in the module map
     • a module in node_modules

    This might be related to the module not being installed or a typo in the module name.

**Why**: The error occurred because the test script could not find the module 'some-module'. This could be due to the module not being installed or a typo in the import statement.

Suggested fix: Ensure that 'some-module' is correctly listed in the dependencies or devDependencies in the package.json file and that it is installed. Also, check for typos in the import statements in the test files.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit