google/kukui: Revise FMAP layout for larger CBFS

Kukui with vboot enabled will build with `detachable_ui`, which needs
larger space in CBFS for more complicated assets. So we need to revise
FMAP sections:

- BOOTBLOCK (not really used) only needs <= 32K.
- GBB can be much smaller since assets moved from GBB to CBFS.
- FMAP is re-ordered (with the cost of less efficient in bsearch) so CBFS can
  get larger continuous space.
- COREBOOT(CBFS) should take all space left.

Since FMAP and COREBOOT have changed location, the system will need to
reflash EC (which contains the new bootblock) as well.

BUG=b:123202015
TEST=Builds and boots on Kukui P1

Change-Id: I22cff99dca8c396c5897c3f6631721af40f3ffbd
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: https://review.coreboot.org/c/31035
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: You-Cheng Syu <youcheng@google.com>
Reviewed-by: Julius Werner <jwerner@chromium.org>

src/mainboard/google/kukui/chromeos.fmd

@@ -1,10 +1,10 @@
 FLASH@0x0 0x800000 {
 	WP_RO@0x0 0x200000 {
 		RO_SECTION@0x0 0x1f0000 {
-			BOOTBLOCK@0 128K
-			COREBOOT(CBFS)@0x20000 0xe0000
-			FMAP@0x100000 0x1000
-			GBB@0x101000 0xeef00
+			BOOTBLOCK@0 32K
+			FMAP@0x8000 0x1000
+			COREBOOT(CBFS)@0x9000 0x1e4000
+			GBB@0x1ed000 0x2f00
 			RO_FRID@0x1eff00 0x100
 		}
 		RO_VPD@0x1f0000 0x10000