feat(cli): option to init via username password, add lint for smoke-test

[anshbansal]

Changes

• Add option --use-password in datahub init to allow easier generation of tokens for admin for initial setup
• Add some error handling to take care of some common mistakes when datahub init is run in configuring gms url leading to connection issues
• Extract out helper method to get frontend session spread out in smoke tests
• Extract out code for managing config file
• Add linting to smoke-test directory
• Ensure CI fails on lint failure in smoke-test

Follow up work todo in separate PR

• Follow up work to ensure these 4 test cases/functionalities are working 0834a74
• Ensure every folder in smoke-test has __init__ otherwise those tests won't work

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[hsheth2]

mostly looks good, just a few comments on code style / docs

thanks for doing this :)

[hsheth2]

mostly looks good

[hsheth2]

this should not be in the setup job, since it'll block the rest of the docker builds

[anshbansal]

That is actually the intention. Lint should cause rest of CI to simply not run. This causes anyone making changes in smoke tests to fail fast. Otherwise CI will wait for docker builds which takes a while before failing.

[hsheth2]

I'm not sure I agree with that - this will add a few minutes of wall clock time to every docker-unified run, which is already the slowest part of our CI. Lint issues are going to be relatively rare in smoke test, so I don't think it makes sense to slow down our CI significantly to avoid a small number of wasted docker builds

Instead the lint should be a separate job so that the docker builds can run in parallel, and we can use something like this https://github.com/orgs/community/discussions/38361 to cancel the other workflows

[hsheth2]

module level docstrings should go at the top and be in """, don't need to use the __help__ thing

[anshbansal]

Going to do this in follow up PR.