cpufreq: interactive: Do not reschedule timer if policy->max changes

Current implementation rearms timer in CPUFREQ_GOV_LIMITS when
policy->max increases. That's because CPUs' timers are not rearmed if
previous frequency evaluation selects policy->max.

With commit 16b90977d0941f2cf623ea58f6bd01ff82c83b25
("cpufreq: interactive: Rearm governor timer at max freq"),
interactive governor timer is always rearmed, and thus timer will
always fire if CPU is busy. There is no need to rearm timer when
policy->max changes.

Remove code related to rearming timer for policy->max change in
CPUFREQ_GOV_LIMITS.

Change-Id: I9c2eb788ab3b1c4cf02fff653cb8919d52752cda
Signed-off-by: Junjie Wu <junjiew@codeaurora.org>