[`firestartr-bootstrap`] `<org>-all` group is added as owner of the default domain & system

[alambike]

Motivation

During the Firestartr bootstrap process for onboarding a new organization, the default group name defined in the configuration file(which corresponds to a GitHub team) is not consistently used across all generated resources.

Instead, in some cases, the virtual group <org>-all is incorrectly assigned as the default value.

This issue becomes visible in:

• The owner association of generated domains

version: "1.0"
name: default-domain
-owner: group:<org>-all
+owner: group:default
description: "The default default-domain of org"

• The owner association of generated systems

version: "1.0"
name: default-system
domain: domain:default-domain
- owner: group:<org>-all
+ owner: group:default
description: "The default system of default-domain"

The problem was identified because the catalog hydration process failed when resolving owner references, as the <org>-all group could not be found.

[info]: Lazy loading GroupClaim-<org>-all with index GroupClaim-<org>-all
[info]: Running grep -r -l --include -E name: "<org>-all"? .
Rendering the system: 
 Lazy Loading: Lazy Loading: Error: Error: GroupClaim-<org>-all not found
Error: Process completed with exit code 1.

This behavior leads to:

• Incorrect ownership metadata
• Inconsistent team mapping
• Catalog hydration failures due to unresolved owner references

Scope

The scope of this issue includes:

• Reviewing the bootstrap logic to ensure the configured team name is consistently propagated to all relevant resources.
• Identifying where <org>-all is being used as a fallback or default value.
• Ensuring that owner references in domains and systems correctly reflect the configured GitHub team.
• Validating that the generated catalog entities reference existing and valid team identifiers.

Acceptance Criteria

• The team defined in the bootstrap configuration file is consistently used across all generated resources.
• No generated resource assigns <org>-all unless it is explicitly configured.
• Domain and system entities correctly reference the intended GitHub team as owner.
• The catalog hydration process completes successfully without owner resolution errors.
• A new bootstrap execution for a test organization validates the corrected behavior.

[frmadem]

@alambike therefore we need to add a new BootstraFile parameter:

• defaultGroup

And a validation:

1. If the defaultGroup is the ones created by default: firestartr and <org>-all there should be no problem
2. It it is different we should check whether the group/team exists or not.