Revert conjurrc key names to match Ruby CLI

[szh]

Desired Outcome

Update the Python CLI to use the older names for the keys in the conjurrc file. This means changing conjur_account => account and conjur_url => appliance_url.

Implemented Changes

When reading or writing .conjurrc:

• conjur_account is now account
• conjur_url is now appliance_url

For now we are still supporting the old keys when reading the conjurrc in order not to break existing installations of the 7.x CLI. This is deprecated and will be removed in a future release.

This fixes incompatibility between this Python CLI and the previous Ruby/Docker based CLI, as well as summon-conjur.

The variable names remain the same. Only the key names are changed.

Connected Issue/Story

CyberArk internal issue link: ONYX-22955

Changelog

• [x] The CHANGELOG has been updated, or
• [ ] This PR does not include user-facing changes and doesn't require a CHANGELOG update

Test coverage

• [x] This PR includes new unit and integration tests to go with the code changes, or
• [ ] The changes in this PR do not require tests

Documentation

• [ ] Docs (e.g. READMEs) were updated in this PR
• [ ] A follow-up issue to update official docs has been filed here: [insert issue ID]()
• [ ] This PR does not require updating any documentation

Behavior

• [ ] This PR changes product behavior and has been reviewed by a PO, or
• [ ] These changes are part of a larger initiative that will be reviewed later, or
• [ ] No behavior was changed with this PR

Security

• [ ] Security architect has reviewed the changes in this PR,
• [ ] These changes are part of a larger initiative with a separate security review, or
• [x] There are no security aspects to these changes

[szh]

Code changes look good! Does this mean we're stuck with the old names forever?

@rpothier In planning we pointed out that the Python CLI is not really supported yet (only Community level) so we're ok with some breaking changes, and that we may want to come back around and change these values at some point in the future but for now there's no real reason to change them.

Could we read both the old and the new and only write the new so we upgrade everyone?

@jtuttle Do you think it's worth adding this in now? Is there a large number of users using the Python CLI?

[jtuttle]

@szh Yeah I guess it's pretty easy to read both so let's go ahead and do that. We can steer people towards one or the other via documentation and deprecation notices.

[szh]

@szh Yeah I guess it's pretty easy to read both so let's go ahead and do that. We can steer people towards one or the other via documentation and deprecation notices.

OK great. I've added that functionality and updated the PR description.