Force besu to stop on plugin initialization errors

[Gabriel-Trintinalia]

PR Description

This PR changes the initialization behaviour of plugins in the BesuPluginContextImpl class by introducing a pluginContinueOnError flag. By default, Besu will not allow plugins to fail during registration and other startup lifecycle stages.

Changes Made

pluginContinueOnError Flag:

• Introduced the --plugin-continue-on-error CLI option (default to false).
• Added a pluginContinueOnError flag to the PluginConfiguration class.

Lifecycle Methods:

• Updated the registerPlugins, beforeExternalServices, startPlugins, and afterExternalServicesMainLoop methods to check the pluginContinueOnError flag. If a plugin fails and the flag is set to true, Besu will log the error and continue running. If the flag is set to false, Besu will throw a RuntimeException and halt.

Usage Example

besu --plugin-continue-on-error=true

In this example, if any plugin fails during registration, before external services, startup, or after external services post main loop, Besu will log the error and continue running. If the --plugin-continue-on-error option is set to false (default), Besu will throw a RuntimeException and halt gracefully, ensuring that plugins cannot fail registration.

[fab-10]

LGTM, just add a CHANGELOG entry and doc-change-required label.

Then I am thinking, that even if it will be a breaking changes, to set the default to true, at least to me it seems the normal behavior to fail in case a plugin has an issue. WDYT?

[Gabriel-Trintinalia]

LGTM, just add a CHANGELOG entry and doc-change-required label.

Then I am thinking, that even if it will be a breaking changes, to set the default to true, at least to me it seems the normal behavior to fail in case a plugin has an issue. WDYT?

I agree with stopping the startup when the plugin fails by default. That is probably the right behaviour in the majority of setups.

[fab-10]

LGTM, just a last rename