Fix Gradle configurations in data-loader module

[brfrn169]

Description

This PR fixes the Gradle configuration in the data-loader module to resolve the release failure.

Related issues and/or PRs

N/A

Changes made

Added some inline comments. Please take a look for the details.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• I have considered whether similar issues could occur in other products, components, or modules if this PR is for bug fixes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

Release notes

N/A

[Copilot]

Pull Request Overview

Updates Gradle configuration in the data-loader module to resolve naming conflicts and adopt the newer base.archivesName DSL.

• Adds a project renaming workaround in settings.gradle to avoid duplicate-name conflicts.
• Replaces deprecated archivesBaseName assignments with the base { archivesName } block in both core and CLI submodules.
• Adjusts the CLI module’s project dependency path and removes an unused root module reference.
• Removes a redundant group declaration from the parent data-loader build.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
settings.gradle	Workaround to rename :data-loader:core project to data-loader-core to avoid naming conflicts.
data-loader/core/build.gradle	Switched from archivesBaseName to base.archivesName; removed conditional shadowJar disabling block.
data-loader/cli/build.gradle	Switched from archivesBaseName to base.archivesName; updated project dependency to :data-loader:data-loader-core and removed the old :core reference.
data-loader/build.gradle	Removed the top‐level group declaration for subprojects.

Comments suppressed due to low confidence (3)

data-loader/cli/build.gradle:17

• The dependency on project(':core') now seems incorrect after renaming the core module. Consider removing it or updating it to the correct path to avoid pulling in the wrong module.

implementation project(':core')

data-loader/core/build.gradle:49

• [nitpick] The conditional disabling of shadowJar was removed, which may lead to fat jars being published unintentionally. Consider documenting this behavior change or restoring the condition if standard JAR publication is still required.

if (project.gradle.startParameter.taskNames.any { it.endsWith('publish') } ||

data-loader/build.gradle:4

• Removing the group setting will change Maven coordinates for all subprojects, which can break downstream consumers. Verify compatibility or document this as a breaking change.

group = "scalardb.dataloader"

[brfrn169]

Deleted this to avoid overriding the scalardb group name. This is the root cause of the release failure.

[brfrn169]

Added this to avoid the name conflicting issue.

[brfrn169]

This is unnecessary. I missed it during the review of the previous PR.

[komamitsu]

LGTM, thank you!

[ypeckstadt]

LGTM. Thank you.

[ypeckstadt]

Merged and working now.