Update to Forge 47.4.6

[SNWCreations]

The Issue

The mod could boot on Forge 47.4.6, so why not just go to that version?

Forge 47.1.3 is TOO OLD to be used with MC 1.20.1, newer version of lots of mods has been on newer Forge.

Related: Sinytra/ForgifiedFabricAPI#239 and Sinytra/ForgeAutoRenamingTool#1

The Proposal

Clarify that the mod is compatible with latest Forge.

I know there might be a lot of mods still not compatible with Connector, but it should not be the reason for being on an out-dated Forge version.

Possible Side Effects

Encourage users to use Connector on MC 1.20.1.
I understand that this branch of Connector may not actively maintained at this moment, but give users chance to try on it.

Alternatives

No. Stay on old Forge? That does not make any change on making the incompatible mods work, but upgrading the Forge version would let us be compatible with more mods that are actively maintained.

Additional Notes

None.

[Su5eD]

This look fine, I'll probably also need to change the README notice not to direct users to 47.1.3. So long as FFAPI is functional on latest forge we can recommend that to users, the major concern around upgrading before was the forge was making a lot of breaking (to us) changes which I think should no longer be the case?

[SNWCreations]

This look fine, I'll probably also need to change the README notice not to direct users to 47.1.3. So long as FFAPI is functional on latest forge we can recommend that to users, the major concern around upgrading before was the forge was making a lot of breaking (to us) changes which I think should no longer be the case?

Forge 1.20.1 is not updated so fast for now, unlike MC 1.21.x. So we can do many workarounds on it, and it would be much more stable than before.
Although it is still possible to have breaking changes happen, it would not occur at a high rate.