test(provisioning_api): Revert AppConfigControllerTest data providers to match strict 'yes'-only validation

The verifyConfigKey check on core.encryption_enabled was reverted to
master's strict $value !== 'yes' in 626fadd per review feedback,
but the test data providers still asserted the broader truthy set
(1/true/YES/on). Drop those entries so the tests match the controller.
This is validation, not storage — IAppConfig::setValueBool's broader
input handling is unrelated.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Stephen Cuppett <steve@cuppett.com>

Author: cuppett

apps/provisioning_api/tests/Controller/AppConfigControllerTest.php

@@ -367,10 +367,6 @@ public static function dataVerifyConfigKey(): array {
 			['dav', 'public_route', ''],
 			['files', 'remote_route', ''],
 			['core', 'encryption_enabled', 'yes'],
-			['core', 'encryption_enabled', '1'],
-			['core', 'encryption_enabled', 'true'],
-			['core', 'encryption_enabled', 'YES'],
-			['core', 'encryption_enabled', 'on'],
 		];
 	}
 
@@ -388,8 +384,6 @@ public static function dataVerifyConfigKeyThrows(): array {
 			['contacts', 'types', ''],
 			['core', 'encryption_enabled', 'no'],
 			['core', 'encryption_enabled', ''],
-			['core', 'encryption_enabled', '0'],
-			['core', 'encryption_enabled', 'false'],
 			['core', 'public_files', ''],
 			['core', 'public_dav', ''],
 			['core', 'remote_files', ''],