chore: update parent version to 2.1.0-incubating in pom.xml

[GOODBOY008]

Summary

This PR bumps the project version from 2.0.1-incubating to 2.1.0-incubating.

Changes

• Updated all pom.xml files to the next feature version (2.1.0-incubating)

Checklist

• Version bumped in all modules
• Commit follows project conventions

[Copilot]

Pull request overview

Bumps the Apache Fesod project’s Maven artifact versions from 2.0.1-incubating to 2.1.0-incubating across the parent POM and all modules to prepare for the next feature release.

Changes:

• Updated root pom.xml project version to 2.1.0-incubating.
• Updated all module pom.xml parent version references to 2.1.0-incubating.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
pom.xml	Bumps the parent/project version to 2.1.0-incubating.
fesod-sheet/pom.xml	Updates module parent reference to 2.1.0-incubating.
fesod-shaded/pom.xml	Updates module parent reference to 2.1.0-incubating.
fesod-examples/pom.xml	Updates module parent reference to 2.1.0-incubating.
fesod-examples/fesod-sheet-examples/pom.xml	Updates module parent reference to 2.1.0-incubating.
fesod-common/pom.xml	Updates module parent reference to 2.1.0-incubating.
fesod-bom/pom.xml	Updates module parent reference to 2.1.0-incubating.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Root POM version was bumped to 2.1.0-incubating, but the property still reads 2.0.1-incubating. Even though it’s currently unused in the build, keeping it out of sync is misleading and may break external tooling or future refactors that adopt CI-friendly versions. Please update to 2.1.0-incubating or remove the property if it’s not needed.

[delei]

LGTM