Remove VRF v1

[RensR]

No description provided.

[github-actions]

CORA - Pending Reviewers

Codeowners Entry	Overall	Num Files	Owners
*	⏳	3	@smartcontractkit/foundations, @smartcontractkit/core
/core/services/job/	⏳	1	@smartcontractkit/foundations, @smartcontractkit/core
/core/services/pipeline/	⏳	4	@smartcontractkit/foundations, @smartcontractkit/bix-framework, @smartcontractkit/core
/core/services/vrf/	⏳	13	@smartcontractkit/dev-services, @smartcontractkit/core
/core/services/pipeline/task.vrf.go	⏳	1	@smartcontractkit/dev-services
/devenv/	⏳	7	@smartcontractkit/devex-tooling
/deployment/	⏳	1	@smartcontractkit/ccip-tooling, @smartcontractkit/ccip-offchain, @smartcontractkit/keystone, @smartcontractkit/operations-platform, @smartcontractkit/core
/.github/**	⏳	1	@smartcontractkit/devex-cicd, @smartcontractkit/devex-tooling, @smartcontractkit/core

Legend: ✅ Approved | ❌ Changes Requested | 💬 Commented | 🚫 Dismissed | ⏳ Pending | ❓ Unknown

For more details, see the full review summary.

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

Failed Test	Failure Summary	Logs
TestJobController_Create_HappyPath	The test failed without a specific error message, indicating an unspecified failure during test execution.	Logs ↗︎
TestJobController_Create_HappyPath	The test failed without a specific error message, indicating an unspecified failure during test execution.	Logs ↗︎
TestJobController_Create_HappyPath/vrf	The test failed due to a panic or runtime exit during execution, indicating an unexpected error or failure in the test process.	Logs ↗︎
TestJobController_Create_HappyPath/vrf	The test failed due to a runtime panic or call to FailNow during the execution of the VRF job creation test.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube IDE