[BUG] Need to update private jar's version to v24.04.1 for spark-rapids v24.04.0 release

[NvTimLiu]

Describe the bug

Sorry this is my mistake. Due to an unexpected script in the automation release testing, I accidentally published some of private jar files on to the Maven Central yesterday.
 
But we are unable to remove the incorrectly published files as only Sonatype administrators have the authority to delete them.
But probably Sonatype will not help delete the wrongly uploaded files.
 
So we won't be able to release the v24.04.0 spark-rapids-private files as planned. 
The workaround is to release a new version, like v24.04.1 spark-rapids-private, and let our v24.04.0 spark-rapids plugin depends on this new version of private jars.
Not too bad there are no use cases of directly depending on the spark-rapids-private release files, so this won't any impact to the customers.
 
We have optimized the automative release process to add a manual confirmation step, to ensure more careful review in future releases, and avoid similar mistakes.