fix(realtime): manipulate URLs using URL object

[grdsdev]

🔍 Description

Change httpEndpointURL to manipulate url using URL JavaScript type.

What changed?

No behavior change, just use correct types for url manipulation instead of string-based manipulation.

Why was this change needed?

To avoid possible security issues with url manipulation.

🔄 Breaking changes

• This PR contains no breaking changes

📋 Checklist

• I have read the Contributing Guidelines
• My PR title follows the conventional commit format: <type>(<scope>): <description>
• I have run npx nx format to ensure consistent code formatting
• I have added tests for new functionality (if applicable)
• I have updated documentation (if applicable)

📝 Additional notes

[coveralls]

coverage: 95.455% (+12.8%) from 82.621%
when pulling 2d8f0b5 on guilherme/realtime-url-manipulation
into 30d8caa on master.

[mandarini]

Nit: I think that wsUrl.pathname === '' pathname here will never be an empty string, but no harm done in leaving this check there!

[grdsdev]

Nit: I think that wsUrl.pathname === '' pathname here will never be an empty string, but no hard done in leaving this check there!

Why it can't be empty @mandarini ?

[mandarini]

Why it can't be empty @mandarini ?

As mentioned in the pathname spec, URLs with hierarchical schemes (ws URLs follow a hierarchical scheme) "always have at least one (invisible) path segment: the empty string. The pathname value for such URLs will therefore always have at least one / character.".

We can leave the empty check though in any case!