feat!: add optional "include" query parameter, replace the Data Shaper with Dynamic Select​

[mihailkitrozoskicodechem]

What Changed?

Implemented control on which related entities to included in the API responses by specifying them in the query parameter.

Refactored the Select flow to replace the Data Shaper with Dynamic Select​

Why?

This feature was added to improve API performance and flexibility by letting clients request only the related data they need, reducing unnecessary data transfer.

The Select refactor was made to prevent unnecessary selection of segments from memory instead of the DbContext

Closes #266

Type of Change

• 🐛 Bug fix (fixes an issue without breaking existing functionality)
• ✨ New feature (adds new functionality without breaking existing features)
• 💥 Breaking change (existing functionality will be affected)
• 📝 Documentation update
• 🔧 Maintenance (refactoring, dependencies, configuration)

How Did You Test This?

What I tested:

Created related entities and manually tested the flow with sending different include/fields query parameter requests.
Cases with regular, nested includes, no include parameter and faulty includes are covered.

Review Checklist

• My code follows the project's style and conventions
• I've reviewed my own code for obvious issues
• I've added comments where the code might be confusing
• I've updated relevant documentation (if needed)
• I've tested my changes and they work as expected

Screenshots / Additional Context

[fvanderflier]

LGTM