console fill: never copy Google session cookies by default (device-bound); own profile in a Chrome started without automation switches

Google binds its session cookies to the device (Device Bound Session Credentials) and signs out
sessions whose cookies look stolen, which can sign the owner out of their real Chrome. The default is
now storebound's own profile per store; storebound starts Chrome itself (--user-data-dir,
--remote-debugging-port=0, no --enable-automation, navigator.webdriver false) and attaches over CDP.
--use-chrome-session google|apple is an explicit opt-in that warns. /signin/rejected is said plainly.

cli/data/flags.json

@@ -291,7 +291,8 @@
    "profile",
    "start-url",
    "step-timeout",
-   "store"
+   "store",
+   "use-chrome-session"
   ],
   "desktop": [
    "channel",
@@ -805,6 +806,7 @@
    "unity",
    "update-bigmac",
    "upload",
+   "use-chrome-session",
    "variant",
    "variants",
    "vendor",
@@ -971,7 +973,7 @@
   "console fill": [
    "storebound console fill                       lists the forms",
    "storebound console fill <form> --dry [--json] the answers and the step-by-step guidance; opens no browser",
-   "storebound console fill <form> [--store apple|play] [--json] [--profile <dir>]"
+   "storebound console fill <form> [--store apple|play] [--json] [--profile <dir>] [--use-chrome-session google|apple]"
   ],
   "desktop": [
    "storebound desktop                 open the app; in an app folder (storebound.config.*) it adds or selects that",