feat: Enhance workflow discovery and conflict resolution from dependencies

[matheusandre1]

Description

Extend build-time resource discovery to scan dependency JJARs

• Register the flow directory as an application archive marker., Produce an AdditionalApplicationArchiveMarkerBuildItem for the configured

• Scan all application archives, not just the root, Change collectWorkflowFiles to walk the root archive first, then every
  other application archive, applying the same extension filter
  (.yaml/.yml/.json) under the configured directory.

• Precedence rules (deterministic): Root archive (application, with test-over-main precedence) always wins
  over dependency-provided workflows with the same identifier
  (namespace:name:version).

Closes: #760

Changes

• Added support for discovering workflow definition files from dependency `jJARs.
• Introduced configuration option quarkus.flow.definitions.scan-dependencies to control this behavior.
• Updated DiscoveredWorkflowBuildItem to track if workflows originate from the application's root archive.

Testing

Test Plan

• Unit tests added/updated
• Integration tests added/updated (if applicable)
• Tested manually (describe below if applicable)

Manual Testing

Checklist

Before submitting this PR, please ensure:

• I ran the full build with integration tests locally: ./mvnw clean install -DskipITs=false
• Code follows the project's code conventions
• Tests have been added/updated to cover the changes
• Documentation has been updated (if user-facing changes)
• Commit messages are clear and follow conventional commits style
• I have read and followed the Contributing Guide
• I have read and comply with the LLM Usage Policy (if applicable)

[github-actions]

🚀 PR Preview fe4caec has been successfully built and deployed to https://quarkiverse-flow-pr-824-preview.surge.sh

[ricardozanini]

Let's park this for after 1.1.0.