fix: Update custom-dialog.js DOM text reinterpreted as HTML

[Shivam7-1]

By using textContent, it will avoid the risk of Dynamic HTML injection, as these properties automatically escape any HTML special characters in the provided text. This helps prevent cross-site scripting (XSS) vulnerabilities by treating the input as plain text rather than interpreted HTML.

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[NeilFraser]

You need to look at what the code is doing. When projects set .innerHTML with HTML tags, one can't change this to either .textContent or .innerText. Doing so would print raw HTML on the user's screen. There are a dozen such changes you've proposed in your history. Please don't keep proposing this breaking change.

Also (after looking at your other PRs), .innerHTML is absolutely safe when used as a getter. There's never a need to change it unless it is being set.