Fix for issue 471 - non-interactive authentication

[lechnerc77]

Purpose

• This PR changes the login procedure for non-SSO to the non-interactive flow (= avoiding the usage of cf login) to enable the handling of several CF spaces
• Fixes [BUG] Automator fails when being run on existing BTP subaccount with CF org #471

Does the PR solve an issue

[X] Yes - Please add issue number: #471 
[ ] No

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Execute the setup of a CF space in a subaccount that already hosts several CF spaces and use basic authentication for the login flow.

What to Check

Verify that the following are valid

• The flow works without the error inappropriate ioctl for device that means "waiting for interactive data entry to select the space"

Other Information

The limitation remains for login via SSO, as there is no non-interactive flow for this setup i.e. the creation of several spaces is not possible. This is an issue with the CF API and not with the btpsa.

[lechnerc77]

Integration test was successful: https://github.com/SAP-samples/btp-setup-automator/actions/runs/4531314583