Removed ModelAccessValidator in favor of Forward Compatilibity Issues

- Model Access Validator causes unnecessary issues in existing integrations.
- Causes merchant to break integration if configured incorrectly.

sample/bootstrap.php

@@ -75,7 +75,6 @@ function getApiContext($clientId, $clientSecret)
             'log.LogEnabled' => true,
             'log.FileName' => '../PayPal.log',
             'log.LogLevel' => 'DEBUG', // PLEASE USE `FINE` LEVEL FOR LOGGING IN LIVE ENVIRONMENTS
-            'validation.level' => 'log',
             'cache.enabled' => true,
             // 'http.CURLOPT_CONNECTTIMEOUT' => 30
             // 'http.headers.PayPal-Partner-Attribution-Id' => '123123123'

sample/sdk_config.ini

@@ -43,16 +43,6 @@ log.FileName=../PayPal.log
 ; with a warning message
 log.LogLevel=INFO
 
-;Validation Configuration
-[validation]
-; If validation is set to strict, the PayPalModel would make sure that
-; there are proper accessors (Getters and Setters) for each model
-; objects. Accepted value is
-; 'log'     : logs the error message to logger only (default)
-; 'strict'  : throws a php notice message
-; 'disable' : disable the validation
-validation.level=disable
-
 ;Caching Configuration
 [cache]
 ; If Cache is enabled, it stores the access token retrieved from ClientId and Secret from the