Separate LookupValue to different classes per LookupKey type
As suggested by: https://github.com/theforeman/foreman/pull/2909#discussion_r46676200
LookupKey has been separated into two classes and LookupValue still has specific logic for each one.
LookupValue should also be separated or at least move the puppet specific logic into a child class.
#8 Updated by Shimon Shtein almost 6 years ago
At least from Puppet separation point of view, we can handle the LookupValue without inheritance.
All we need to do, is rename use_puppet_default to something more generic.
I have already opened an issue for that: [[http://projects.theforeman.org/issues/15846]]