Issue Summary

leading and trailing whitespace in pipelines variable values is preserved by the backend but is not accurately represented in the UI

leading and trailing whitespace in pipelines variable values is preserved by the backend but is not accurately represented in the UI. post-saving the variable (e.g., a non-secured variable like "<leading space>test"), the value is shown without the leading space after being saved in the UI, but the backend does save it with the leading space.

the value, when fetched from the API, is also preserved with leading and trailing spaces. however, the UI doesn't indicate that the value is stored with spaces, and there is no warning while saving them, which creates confusion.

Steps to Reproduce

1. Step 1 add a leading space and save a text string as a non-secured variable value, e.g., "<leading space>test".

Expected Results

the leading space should be evident and visible in the variable value in the UI, similar to how underscores (_) and other characters are displayed.

Actual Results

post-saving, notice that the UI displays the stored value without any visible leading space.

Workaround

click on "edit" on the value to notice the leading or trailing space, or use the API to fetch non-secured variables to validate them for any leading/trailing spaces. we need to add better warnings or clear text rendering in such cases while saving.