Change Confirmations to Confidence

[EasterTheBunny]

Confidence is a different approach to mapping a chain agnostic concept of confidence that an event or transaction can or should be acted on. Confidence is intended to map to defined levels of confirmations on EVM chains and other states on other chains.

Only two levels of Confidence exist by default to define the boundaries: Highest and Lowest. This creates an inclusive range for all chain configurable Confidence levels and can be treated as % confidence that an event or transaction can or should be acted on.

[github-actions[bot]]

I see you updated files related to core. Please run pnpm changeset 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.

[cl-sonarqube-production[bot]]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
73.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube