Create and publish Besu BOM (Bill of Materials)

[fab-10]

PR description

Introducing Besu BOM (bill of materials) to improve the way we manage shared dependencies between Besu and plugins.
It is based on Gradle Java Platform plugin and it is also used internally, replacing the Spring Dependency Manager, it is then published as BOM artifacts so it can be used as reference in plugins for all the dependencies that are in common with Besu, this way it is easier to spot dependencies incompatibilities when developing plugins.

Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[garyschulte]

This looks clean, but could you provide a description and motivation for the change?

[fab-10]

Thanks @garyschulte, I just forgot to add it, done now.

[siladu]

Looks good, just couple of questions...

Does this PR have any impact on the license report?

besu/build.gradle

Lines 113 to 114 in 0d63955

	// If set to true, then all boms will be excluded from the report
	excludeBoms = true

[fab-10]

Looks good, just couple of questions...

Does this PR have any impact on the license report?

besu/build.gradle

Lines 113 to 114 in 0d63955

	// If set to true, then all boms will be excluded from the report
	excludeBoms = true

I have checked and the licenses are checked and the report is produced as before.

[siladu]

LGTM thanks for answering my questions