Add old package name to "replace" in composer.json

[koehnlein]

In c5b02cd043e15326fb7e856c39b8fa02d1abed37 the composer package was renamed from "codeception/visualception" into "codeception/module-visualception".

This pull requests adds the old name to "replace" section in composer.json. With this change, composer knows that the new package "codeception/module-visualception" (new) must not be installed together with "codeception/visualception" (old)

[ggiak]

Hey @koehnlein, good idea, however the new version requires codeception 5 while the old one requires-dev codeception: 2.5.6

[koehnlein]

@ggiak Interesting. I thought, the renaming would only happend after the release of 5.0.0 - but you are right, the renaming already was part of the 5.0.0 tag here on GitHub.

But then I wondered, why I have installed codeception/visualception:^5.0 in my projects and I think, I found the problem: The package is still published on packagist with its old name: https://packagist.org/packages/codeception/visualception it does not exist at all with its new name https://packagist.org/search/?query=codeception%2Fmodule-visualception

So the first step to fix this confusing situation, I would suggest to stop the GitHub/packagist sync to the old package "codeception/visualception".
After that, it would be great to have this PR merged, have a new release 5.0.1 or 5.1.0 or something and also have a new GitHub/packagist sync to the correct updated package name.
As last step I would suggest to add an "abandoned": "codeception/module-visualception" information into the old packagist package. You can do that on the packagist website, if you have the correct permissions.