…ding blocks

meshstack Terraform provider v0.24.4 renames spec.parent_building_blocks of
meshstack_building_block to spec.parent_building_block_refs and turns every
element into a meshObject ref of kind and uuid. meshStack derives the parent
definition from the referenced building block, so the definition uuid is not
sent any more. The same release adds a computed ref output on
meshstack_building_block, so each child points at the parent resource with a
single expression.

The aks starterkit and the ske starterkit are the only places in the hub that
declare a parent relation between building blocks. Both raise the meshstack
provider constraint to >= 0.24.4, because the new attribute does not exist
before that release.

The variables that fed the old definition uuid stay: the aks starterkit keeps
var.github_repo_definition_uuid, and the ske starterkit keeps the uuid member of
var.building_block_definitions, because meshstack_integration.tf still passes
both and removing them would change the module interface.

Refs: meshcloud/terraform-provider-meshstack#273

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…arter kit

No resource in modules/ske/ske-starterkit/buildingblock reads the definition
uuid any more. Each child building block names its parent through
spec.parent_building_block_refs, and meshStack derives the definition of the
parent from the referenced building block. Both call sites read only the
version ref of a definition.

The variable therefore carries only what the module reads. It keeps the map and
the keys "git-repository" and "forgejo-connector", but the value of each key is
now the version ref alone, and the name says so: building_block_definitions
becomes building_block_definition_version_refs.

meshStack fills the variable in as a static input of the building block
definition, so both sides move together. meshstack_integration.tf renames the
input and the variable that the input encodes, and the e2e test passes the
version_ref member of the building_block_definition output of each module that
owns a definition.

A caller of the module modules/ske/ske-starterkit renames the argument and
passes module.<name>.building_block_definition.version_ref instead of
module.<name>.building_block_definition. The building_block_definition output of
the starter kit itself does not change.

Refs: meshcloud/terraform-provider-meshstack#273

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

The description of the map said which member of which output a caller passes, and why the definition
uuid is not part of it. The first is a fact about another module, the second explains an absence.
Neither tells the reader what the map is, so both go, and the type says the rest.

The comment above the variable keeps the one fact the code cannot show: the input in
meshstack_integration.tf fills the map in, so the two names have to move together.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>