[MANY] Fixed require versions for 2.3-dev projects.



| Q             | A
| ------------- | ---
| License       | MIT

It looks to me like a 2.2 merge into master caused a bunch of Composer incompatibilities. For example, requiring Framework bundle 2.3.* will try to require symfony/dependency-injection 2.2.*. This is probably not what is expected.

The following composer.json shows the behavior:

~~~ json
{
    "require": {
        "symfony/http-kernel": "2.3.*"
    },
    "minimum-stability": "dev"
}
~~~

Output:

~~~
Loading composer repositories with package information
Installing dependencies
  - Installing psr/log (1.0.0)

  - Installing symfony/http-foundation (2.2.x-dev v2.2.0-RC1)
    Cloning v2.2.0-RC1

  - Installing symfony/event-dispatcher (2.2.x-dev v2.2.0-RC1)
    Cloning v2.2.0-RC1

  - Installing symfony/http-kernel (dev-master 164dd88)
    Cloning 164dd884b88382dd8e37caa43a534553a4887b98

symfony/event-dispatcher suggests installing symfony/dependency-injection (2.2.*)
symfony/http-kernel suggests installing symfony/browser-kit (2.2.*)
symfony/http-kernel suggests installing symfony/class-loader (2.2.*)
symfony/http-kernel suggests installing symfony/config (2.2.*)
symfony/http-kernel suggests installing symfony/console (2.2.*)
symfony/http-kernel suggests installing symfony/dependency-injection (2.2.*)
symfony/http-kernel suggests installing symfony/finder (2.2.*)
Writing lock file
Generating autoload files
~~~

I did a blanket sweep on anything requiring symfony/* 2.2.* and replaced with 2.3.*. If there are any legitimate cases where symfony/* 2.2.* should be used this might have broken that.