Over time Convert2RHEL have been using python logging incorrectly and it's gotten to a point where it's painful to develop with when you have tooltips or otherwise want to initialize and log debug items depending on user input

Not only that, but we currently hardcode what stage we're in within the log messages themselves rather than letting a custom logging module handle it. This creates an issue where we may have typos or simply forget to log the stage properly. Or otherwise just mix stages up that shouldn't be split

Acceptance Criteria

• Refactor logging to avoid overriding python logging module
• Reduce custom decisions that fall outside of python logging standards
• Move log indicators from the logging entries to a custom logging class (e.g. logging a message "Rollback: something something" instead of letting logging class handle it)
• Always write debug to file
• Implement dynamic option assignment to help with toolopts parsing happening later