cpufreq/zzmoove: add profiles_sticky_mode

in some situations it may be useful to tweak profiles without
profile_number reverting to 0. granted, this carries the risk
of not being able to tell if the profile is fully applied or not.
however, for my usage i'd rather it not always jump to the ambiguous
"custom" profile.

- profiles_sticky_mode
   0 = normal (profile "breaks" when any tuneable changed)
   1 = sticky mode (profile stays intact, even if a tuneable changes)

in the future, a sysfs can be made to verify the integrity of the
currently set profile.
cpufreq/zzmoove: keep dynamic tuneables constant, typingbooster bugfix

dbs_tuners_ins.sampling_down_factor and dbs_tuners_ins.sampling_down_max_mom
dynamically change, which in turn makes some utilities go crazy.

this commit allows the tuneables to remain constant, while a duplicate variable
is deals with the governor's dynamic values.

also includes a bugfix for the typingbooster, in the form of the added _saved
variables in the up_threshold and hotplug_min_limit portion of set_profile().