Fix: handle nullish values in template sinks with ?? operator

[the-matrixneo]

This PR addresses a bug where plain objects with a primitive .value property { value: 0 }) were incorrectly processed by the rml parser.
these effects were considered

• rendering as HTML content <div>${expr}</div>.
• when rendered inside an element's attribute <input value="${expr}">.

The Fix:

• new logical check has been added to the beginning of the data sink processing logic in the main rml function.
• this check now correctly identifies these "value-wrapper" objects and extracts their primitive value.

Please add hacktoberfest label

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[dariomannu]

This change block seems redundant. Everything works well with the other change alone.
Let's get rid of this, then we are good, by the looks of it.

[the-matrixneo]

completed!

[dariomannu]

These are great, could you please move them inside the BehaviorSubject block?

[the-matrixneo]

done!