Replaced short array syntax usages with traditional array syntax

[aik099]

The short array syntax was accidentally introduced in the #407.

If there is a need, then we can mass-convert driver code to use short array syntax (e.g. using PHP_CodeSniffer rule or PhpStorm inspection).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.07%. Comparing base (2cd7d77) to head (efb7309).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #411   +/-   ##
=========================================
  Coverage     86.07%   86.07%           
  Complexity      184      184           
=========================================
  Files             1        1           
  Lines           510      510           
=========================================
  Hits            439      439           
  Misses           71       71           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[uuf6429]

I'm not a fan of this change since:

• in my eyes, it's a downgrade
• it still isn't the proper way of telling devs what kind of coding style is allowed
• it would have been automated and more future-proof if done through PHP-CS-Fixer (or similar)

In practices, since it's harmless, I'm fine with approving it.

[aik099]

• in my eyes, it's a downgrade

Syntax is syntax. Use whichever that works but be consistent throughout the codebase. This wasn't the case, hence this PR.

Anyway this PR is a transient step (as I've probably mentioned elsewhere) to keep syntax consistent. In another PR you can perform system-wide (driver code & driver tests) syntax change to short array declaration (you can use tools shown in the PR description).

• it still isn't the proper way of telling devs what kind of coding style is allowed
• it would have been automated and more future-proof if done through PHP-CS-Fixer (or similar)

Completely agree. I'm open to suggestions. Please create an issue where we can discuss our options. We can later apply same concepts to the mink/webdriver-classic-driver as well.

In an ideal world:

• use a consistent code style across the codebase
• stick to a coding standard (the PSR2 is used currently)
• use a more strict coding standard
• fail the build when PR code doesn't follow the standard

What we have now:

• the PSR2 standard doesn't care about array declarations
• coding style isn't automatically checked for PRs

.