stacks: allow removed blocks to target components in nested stacks

[liamcervante]

This PR updates removed blocks in stacks so that you can target components within nested stacks. This means that users can change input values into embedded stacks that might edit the number of components internally, and add removed blocks within the root stack that target any components removed by the change.

The general approach is that the from attribute of removed blocks now resolves to a full absolute address. Stack instances are now initialised with any external removed blocks in the constructor. So parent stacks pass in any removed blocks they have that target child stacks directly into the child stack. Then the removed blocks are still processed by the stack that actually contains the components that they target, this allows us to ensure that component and removed blocks don't target the same instance easily, and that removed blocks defined locally don't clash with removed blocks defined externally.

[liamcervante]

not correct! we need to combine the addresses properly

stackaddrs.ConfigComponent{
Stack: append(stackAddr, rc.From.ConfigComponent().Stack)
Component: rc.From.ConfigComponent().Component
}

[dsa0x]

Or simply c.From.ConfigComponent().String()? The definition already contains the stack string

func (ist InStackConfig[T]) String() string {
...
return ist.Stack.String() + "." + ist.Item.String()

[liamcervante]

we do need to combine it with the other stack address as the from address is relative, and we want to provide the absolute address here.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.