Catch conflicts when multiple parameters in the same scope get renamed to the same name

[Matyrobbrt]

The previous conflict checking did not check for parameters in the same scope being renamed to the same name which could lead to ambiguous references after JST is applied and in turn behavioural differences.
Fixes #44

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 49b8048db936956308d8e19589ff0ee16e2d973a.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged.jst:jst-api:1.0.71-pr-48-gh-44
• 📦 net.neoforged.jst:jst-cli:1.0.71-pr-48-gh-44
• 📦 net.neoforged.jst:jst-cli-bundle:1.0.71-pr-48-gh-44

Repository Declaration

In order to use the artifacts published by the PR, add the following repository to your buildscript:

repositories {
    maven {
        name 'Maven for PR #48' // https://github.com/neoforged/JavaSourceTransformer/pull/48
        url 'https://prmaven.neoforged.net/JavaSourceTransformer/pr48'
        content {
            includeModule('net.neoforged.jst', 'jst-api')
            includeModule('net.neoforged.jst', 'jst-cli')
            includeModule('net.neoforged.jst', 'jst-cli-bundle')
        }
    }
}

[neoforged-releases]

🚀 This PR has been released as JavaSourceTransformer version 1.0.70.