`jerk:get_value/2` should raise a different error when the attribute is undefined

Currently fails with `error(badarg)`; however, this is ambiguous because it could also mean that a value that is not a Jerk term was passed or a attribute name that is not a binary. It would be better to differentiate between these cases and the case where an attribute is undefined by raising something like `badattribute` instead of `badarg`.