AlgoKit maintainers can trigger portability tests to verify validity of pyinstaller binaries

[aorumbayev]

Description

The goal is to introduce a set of portability tests that ensures the following:

• AlgoKit maintainers have higher confidence in identical behaviour on wheel vs binary execution mode when releasing new features
• Improving the ability to track regression between releases of algokit cli

Technical Details

Introduce a set of tests to run against a fresh pyinstaller binary to verify main functionality of the algokit cli:

• doctor
• init
• bootstrap
• task vanity-task
• localnet

Acceptance Criteria

1. AlgoKit maintainers can rely on automation pipelines to verify validity of new functionality within the context of binary execution mode
2. AlgoKit maintainers can quickly spot compatibility issues and regression in binary execution mode between algokit cli releases

Tasks

• Introduce a new pytest python file separate from algokit cli approval tests that covers triggers of specific commands and asserts valid exit codes
• Introduce extra step into github actions pipelines to trigger this script via pytest after binary is build.