Ignore auth failures when trying to pull apps during cli login

[keyallis]

This has been causing failures in e2e

Checklist

• The title of this PR would make a good line in Acorn's Release Note's Changelog
• The title of this PR ends with a link to the main issue being address in parentheses, like: This is a title (#1216). Here's an example
• All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
• Commits follow contributing guidance
• Automated tests added to cover the changes. If tests couldn't be added, an explanation is provided in the Verification and Testing section
• Changes to user-facing functionality, API, CLI, and upgrade impacts are clearly called out in PR description
• PR has at least two approvals before merging (or a reasonable exception, like it's just a docs change)

[g-linville]

I'm a bit confused; why are we getting auth failures in the first place?

[keyallis]

If we are logged in as a user that doesn't have permissions to pull apps in a given project and then we try to log in as another user. What we're seeing in e2e is that when we log in as a non-permissioned user for rbac tests and then try to log back in as the default e2e user we fail to pull app information and then never actually log in because the cli never attempts to do the auth login flow once we fail to pull apps

[g-linville]

Why does logging in try to pull app information?

[keyallis]

That would be a question for @ibuildthecloud