Internal or external links are not correctly detected on schema agnostic urls

Problem/Motivation

When parsing URLs, schema-agnostic URLs (for example:

//www.mydomain.com/foo/bar) are incorrectly detected as internal links.

This happens because in setIfExternalOrInternal(), the detection logic checks for the presence of a schema to determine whether a link is external or internal. Since schema-agnostic URLs do not include a schema (e.g. http: or https:), the function treats them as internal and returns early, preventing further processing of the URL components.

As a result, these URLs are not correctly identified as external, and subsequent logic that depends on a complete URL breakdown (host, path, etc.) does not execute properly.

Steps to reproduce

1. Create or load an entity that contains a field or markup with a schema-agnostic URL (e.g. //example.com/foo/bar).
2. Trigger the processing path where setIfExternalOrInternal() is invoked.
3. Observe that the function returns early, marking the URL as internal.
4. As a result, the host and other URL components are never populated.

Proposed resolution

Update setIfExternalOrInternal() to correctly handle schema-agnostic URLs:

• Detect host and scheam, not only schema

Remaining tasks

• Detect host and scheam, not only schema

User interface changes

None.

API changes

None.

Data model changes

None.