Aliasfy Packages are ignored in the Pool Preperation

[Schuchie]

Describe the bug
Aliasfy packages are filtered from the pool preparation command through the following change:

• Aliasfied packages are ignored in Validate with Release Config dxatscale/sfpowerscripts#1289
• sfp/packages/sfp-cli/src/impl/parallelBuilder/BuildImpl.ts:415

To Reproduce
Steps to reproduce the behavior:

1. Have a aliasfy package in the sfdx-project.hson and executed the pool preparation command without an release-config:
2. sfp orchestrator:prepare -f config/project-ci-stage-pool-def.json -v devhub --loglevel trace
3. The builded packages does not contain any aliasfy package

Expected behavior
Aliasfy packages are included in the pool creation. It should take the "default"-Package if exists.

Screenshots
If applicable, add screenshots to help explain your problem.

Platform Details (please complete the following information):

• OS: MacOs/Ubuntu
• Version [e.g. CLI Version eg: 1.6.6]: @flxbl-io/sfp/38.3.0 darwin-arm64 node-v20.6.1
• Salesforce CLI(sfdx cli) Version: @salesforce/cli/2.30.8 darwin-arm64 node-v20.6.1
• CI Platform: GitHub

Additional context
The following line of code is filtering aliasfy packages in the pool creation:

• Aliasfied packages are ignored in Validate with Release Config dxatscale/sfpowerscripts#1289
• sfp/packages/sfp-cli/src/impl/parallelBuilder/BuildImpl.ts:415

[dieffrei]

@azlam-abdulsalam any thoughts, on this one?
I think it makes sense, usually, you could have a default configuration you want to deploy to scratch orgs

[dieffrei]

@Schuchie fyi this feature will be available on aliasifyv2, however, there is no ETA yet, as it is under development.