ci: add top-level workflow orchestrator

[ndonkoHenri]

https://github.com/flet-dev/flet/actions/runs/21566901473

Summary by Sourcery

Introduce a top-level CI workflow that orchestrates reusable build, release, and macOS integration test workflows based on detected file changes.

Build:

• Split the monolithic CI workflow into a lightweight orchestrator that conditionally calls a reusable build-and-release workflow and a macOS integration tests workflow using changed-file detection.
• Extract the existing build, packaging, publishing, and release jobs into a dedicated build-and-release reusable workflow with shared environment and concurrency configuration.
• Convert the macOS integration tests workflow into a callable workflow so it can be triggered from the main CI orchestrator instead of on every push/path change.

[sourcery-ai]

We've reviewed this pull request using the Sourcery rules engine

[cloudflare-workers-and-pages]

Deploying flet-docs with    Cloudflare Pages

Latest commit:	61385fd
Status:	✅  Deploy successful!
Preview URL:	https://5e1a35ee.flet-docs.pages.dev
Branch Preview URL:	https://unify-github-actions.flet-docs.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying flet-examples with    Cloudflare Pages

Latest commit:	61385fd
Status:	✅  Deploy successful!
Preview URL:	https://4e6bc1b9.flet-examples.pages.dev
Branch Preview URL:	https://unify-github-actions.flet-examples.pages.dev

View logs

[FeodorFitsner]

Isn't it easier to specify files filter on each workflow instead?

[ndonkoHenri]

Isn't it easier to specify files filter on each workflow instead?

Its possible, yh. But the main goal of this PR is to have one main ci dashboard.

I find it personally easier to navigate through the ci workflows for each ref/commit, as its all on one spot, especially as we now going to have 3 workflows all usually running at the same time. But let me know what you think.