PXP-638: [CLI] Implement new config

[mfauzaan]

Summary

Build the workflow for the wukong init command to satisfy the specifications. Details about the command inputs and outputs can be found here.

Ticket: https://mindvalley.atlassian.net/browse/PXP-524

What's Changed

• Update the Google auth to store in our config file instead of a separate file
• Update all auth logics to refer to new path
• Add google cloud and vault login to wukong init
• Updated wukong login logic to use same function on wukong init to avoid duplicate codes

[Fadhil]

Ok. This looks good to go. We're mostly refactoring some config vars to use the new format with an auth section. Let's test it out.

[jk-gan]

As I know, wukong init command should re-initialize the config file. How about the UX in this scenario:
The user had already logged in google cloud and bunker, but they choose to not log in when they run wukong init. Should we remove the existing google cloud and bunker credentials from the newly generated config file?

@onimsha @mfauzaan

[onimsha]

As I know, wukong init command should re-initialize the config file. How about the UX in this scenario: The user had already logged in google cloud and bunker, but they choose to not log in when they run wukong init. Should we remove the existing google cloud and bunker credentials from the newly generated config file?

@onimsha @mfauzaan

Yeah I think it's the right approach. Because when a user re-init the config, at the end of the initialisation process, they will have to review the config before writing it to disk, so it wouldn't make sense if we keep some of the old configuration.

[sauron-droid]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mfauzaan, onimsha

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment