feat(releases): add config flag to enable/disable nested release linking

[bibhuti230185]

Summary

Add a configuration flag to enable/disable the nested release (release-to-release linking) feature in the frontend. This feature allows organizations to control whether users can link releases to other releases based on their compliance policies.

Changes

New Configuration Key

• Added IS_NESTED_RELEASE_ENABLED (nested.release.enabled) to ConfigKeys enum

Conditional UI Rendering

When the configuration is disabled (nested.release.enabled = false), the "Linked Releases" tab and content are completely hidden in:

File	Description
EditRelease.tsx	Release edit page
AddRelease.tsx	Release add page
DetailOverview.tsx	Release detail view page
CurrentReleaseDetail.tsx	Moderation request release view
MergeReleaseDataCheck.tsx	Release merge page

Behavior

Config Value	Behavior
true (default)	Linked Releases tab is visible and functional
false	Linked Releases tab is completely hidden
Not set / null	Defaults to true (enabled)

Backend Dependency

Requires: eclipse-sw360/sw360#4239

Testing

1. Set nested.release.enabled = false in SW360 configuration database
2. Navigate to any release page (add/edit/detail)
3. Verify "Linked Releases" tab is not visible
4. Set nested.release.enabled = true or remove the config
5. Verify "Linked Releases" tab is visible and functional