Move to Gradle v7.6.3 for all wrappers.

[benjsmi]

As per https://nvd.nist.gov/vuln/detail/CVE-2023-44387, Gradle v7.6.2 is vulnerable. Moves all incorporate wrappers to the latest version of Gradle in their properties spec such that they use the latest Gradle (on the 7.6.x branch) to run the build.

Related to #312 but not mentioned explicitly in that issue.

[benjsmi]

Merged in other merged PR for org.json to this PR to avoid conflicts.

[benjsmi]

@bestbeforetoday -- do you mind reviewing this?

[benjsmi]

@bestbeforetoday Read up on the right way to upgrade Gradle Wrapper and have applied those changes to this PR now. Thanks for the tip!

[bestbeforetoday]

It looks like you might have missed the Gradle wrapper upgrade in the examples/fabric-contract-example-gradle-kotlin directory. Also the commits all need a signoff statement (git commit --amend --signoff)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[benjsmi]

@bestbeforetoday yeah I definitely ran the wrapper command in the Kotlin directory.

programsam@Bens-IBM-Laptop-2022 fabric-contract-example-gradle-kotlin % ./gradlew wrapper --gradle-version 7.6.3
Starting a Gradle Daemon (subsequent builds will be faster)

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 7s
1 actionable task: 1 up-to-date

Oddly enough, the JAR file in that directory does not/did not seem to need changing. Not sure why that is.