fix(user-settings): enhance build-info config to make it intuitive

[debsmita1]

Description

Renamed the buildInfo.full property to a more intuitive name for clarity. The old name (full) was ambiguous and didn’t clearly convey its purpose.

Replaced full with overrideBuildInfo

Functionality still remains the same
true → displays only the explicitly configured information

false → displays configured information alongside build versions

Made the change backward compatible for users who already have full: false in their configuration.

Which issue(s) does this PR fix

• Fixes https://issues.redhat.com/browse/RHDHBUGS-462

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign schultzp2020 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3444
• quay.io/rhdh-community/rhdh:pr-3444-a7d15693

[openshift-ci]

@debsmita1: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-tests	a7d1569	link	true	/test e2e-tests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.