Improved Factor and Device Token Handling

[Sector95]

If the desired preferred factor doesn't exist, it will now list all available factors instead of displaying an empty list. Further, if a device token doesn't exist in the configuration file, it will be created on the first run instead of requiring the user to run the tool again with the --action-register-device flag.

Related Issue

#93

Motivation and Context

Bad user experience having to run the tool again for the device token, and then an even worse experience when shown an empty list of factors, and no good reason as to why.

How Has This Been Tested?

Unit and user acceptance testing.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.