testing/linux-edge: enable CONFIG_PINCTRL_CHERRYVIEW=y

Fixes keyboard on Chromebook Terra.

Loading pin control as a module appears to have unexpected behavior.
Relevant comment in a discussion thread on Intel_Strago Chromebooks:

  https://bugzilla.kernel.org/show_bug.cgi?id=194945#c95
  Dmitry Torokhov:

  Can you try making CONFIG_PINCTRL_CHERRYVIEW=y ? I have no idea what
  happens when pin control is loaded late in the boot process.

Notice that CONFIG_PINCTRL_BAYTRAIL is already built in for the same
reason.
10 jobs for !16078 with linux-cherryview in 327 minutes and 50 seconds (queued for 1 second)
latest detached
Status Job ID Name Coverage
  Lint
failed #277787
docker-alpine x86_64 allowed to fail
lint

00:00:20

 
  Build
passed #277792
docker-alpine ci-build aarch64
build-aarch64

00:45:29

passed #277793
docker-alpine ci-build armv7
build-armv7

00:44:40

passed #277791
docker-alpine ci-build ppc64le
build-ppc64le

00:00:51

passed #277790
docker-alpine ci-build s390x
build-s390x

00:00:50

passed #277789
docker-alpine ci-build x86
build-x86

00:00:19

passed #278056
docker-alpine x86_64 ci-build
build-x86_64

04:42:00

failed #277788
docker-alpine ci-build x86_64
build-x86_64

01:00:05

failed #277801
docker-alpine x86_64 ci-build
build-x86_64

01:00:05

failed #277838
docker-alpine x86_64 ci-build
build-x86_64

03:00:08

 
Name Stage Failure
failed
lint Lint
No job log