PSR2/PropertyDeclaration: update for properties with asymmetric visibility [1]

Per the FIG PSR-PER updates (next version), the "properties must have visibility declared" rule is also satisfied if only write visibility is declared.

> The `public` keyword MAY be omitted when using a set-visibility on a public-read property.

Includes updated test expectations (on the tests previously added in 871).

Refs:
* php-fig/per-coding-style 99
* php-fig/per-coding-style 114

Author: jrfnl

src/Standards/PSR2/Sniffs/Classes/PropertyDeclarationSniff.php

@@ -114,7 +114,7 @@ protected function processMemberVar(File $phpcsFile, $stackPtr)
             }//end if
         }//end if
 
-        if ($propertyInfo['scope_specified'] === false) {
+        if ($propertyInfo['scope_specified'] === false && $propertyInfo['set_scope'] === false) {
             $error = 'Visibility must be declared on property "%s"';
             $data  = [$tokens[$stackPtr]['content']];
             $phpcsFile->addError($error, $stackPtr, 'ScopeMissing', $data);

src/Standards/PSR2/Tests/Classes/PropertyDeclarationUnitTest.php

@@ -61,9 +61,8 @@ public function getErrorList()
             95  => 1,
             96  => 1,
             97  => 2,
-            101 => 2,
+            101 => 1,
             105 => 1,
-            107 => 1,
         ];
 
     }//end getErrorList()