[Bug]: Fix BAL_CONFIG_DATA toml parsing not throwing parsing errors

[HindujaB]

Description

$subject

Steps to Reproduce

Currently, if we provide invalid TOML content through the Environment Variable, it throws value not provided errors for configurable instead of an Invalid TOML content error.
This is deviant from the TOML file passing behavior.

This is because we ignore the diagnostic logs from the Toml parser if we receive a valid toml node.

Affected Version(s)

current master

OS, DB, other environment details and versions

No response

Related area

-> Runtime

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.