[incubator-kie-drools#5758] Update drools-docs for v10

[tkobayas]

• Also removed some unused attributes

Issue:

• Update drools-docs for v10 #5758

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

• for pull request and downstream checks

  • Push a new commit to the PR. An empty commit would be enough.

• for a full downstream build

  • for github actions job: add the label run_fdb

• for Jenkins PR check only

  • If you are an ASF committer for KIE podling, login to Jenkins (https://ci-builds.apache.org/job/KIE/job/drools/), go to the specific PR job, and click on Build Now button.

[tkobayas]

@baldimir @mariofusco Please review, thanks!

This PR is just to make the docs consistent with version 10 instead of version 8.

If we will make a big change and/or integrate with the new website, it would be another issue/PR.

[baldimir]

I think the minimal Maven version is now 3.9.3. Is that correct @jstastny-cz please?

[tkobayas]

drools itself is 3.8.6 https://github.com/apache/incubator-kie-drools/blob/main/build-parent/pom.xml#L89

But actually, our GHA runs with 3.9.3 to meet Quarkus 3.2 LTS <proposed-maven-version>3.9.3</proposed-maven-version>.

I'm good with changing the doc to 3.9.3 as a requirement.

[baldimir]

Thank you for clarification. Then I think the doc is fine. If we will find that the Maven version would be good to update, it can be done in a separate PR.