Add device policy: Kiosk Virtual Keyboard Layout.

chrome/test/data/policy/policy_test_cases.json

 {
   "-- Template --": {
     "intro": "Top-level entries map a policy name to its test parameters, described below. The name of the top level entry should be of the form <policy name>[.suffix]. The optional suffix is used for defining multiple test cases for a single policy.",
 
     "os": ["List of operating systems that support this policy. Valid values:", "win", "linux", "mac", "chromeos", "Defaults to empty if not specified."],
     "official_only": "Whether this policy exists in official builds only. Defaults to |false| if not specified.",
     "can_be_recommended": "Whether a recommended value may be set for the policy. Defaults to |false| if not specified.",
     "test_policy": "A policy dictionary that should make the preferences affected by this policy become policy-controlled. Usually just sets the current policy. Defaults to an empty dictionary if not specified.",
     "note": "If the policy affects any preferences, the following array should be specified with one entry per such preference.",
     "pref_mappings": [
@@ skipping 2265 matching lines @@
 
   "SupervisedUsersEnabled": {
   },
 
   "SupervisedUserCreationEnabled": {
   },
 
   "AutoCleanUpStrategy": {
   },
 
+  "TouchVirtualKeyboardEnabled": {

[bartfab (slow), 2014/06/13 12:15:53]

You should provide a proper test case for this. Only device policies are exempt
from this because they are set via a different mechanism that the test cannot
easily invoke.

[rsadam, 2014/06/13 15:28:46]

Done.

+  },
+
   "----- Chrome Frame policies -------------------------------------------": {},
 
   "ChromeFrameRendererSettings": {
   },
 
   "RenderInChromeFrameList": {
   },
 
   "RenderInHostList": {
   },
 
   "ChromeFrameContentTypes": {
   },
 
   "GCFUserDataDir": {
   },
 
   "AdditionalLaunchParameters": {
   },
 
   "SuppressChromeFrameTurndownPrompt": {
   },
 
   "SkipMetadataCheck": {
   }
 }