Update `Hyde::asset()` method to consider protocol relative URLs `//` to be remote

[emmadesilva]

We may also want to check we use this across the board.

The featured image class uses the following: (Maybe we move it to the Hyperlinks class?)

public static function isRemote(string $source): bool
{
    return str_starts_with($source, 'http') || str_starts_with($source, '//');
}

[emmadesilva]

Claude naming response

Given the context you've provided about HydePHP, its philosophy, and target audience, let's reconsider the method name. The current name isRemote is concise, but we might be able to make it even more intuitive and self-explanatory.

Here are some alternative suggestions for the method name, along with their pros and cons:

1. isExternalUrl
   Pros: Clearly indicates that it checks if a URL is external to the site.
   Cons: Slightly longer than isRemote.

2. isOffSiteLink
   Pros: Intuitive for both developers and non-developers.
   Cons: Uses "link" which might be less precise than "URL".

3. isExternalResource
   Pros: Comprehensive, covering both URLs and other types of external resources.
   Cons: Might be too broad for its specific function.

4. pointsToExternalSite
   Pros: Very descriptive and clear about what it does.
   Cons: Longer than the other options.

5. isOutboundUrl
   Pros: Concise while still being clear about its purpose.
   Cons: "Outbound" might be less immediately understood by some users.

Considering HydePHP's motto "Simplicity first. Power when you need it. Quality always." and the focus on intuitive APIs, I would recommend isExternalUrl as the best balance between clarity and conciseness.

This name:

1. Is self-explanatory, even for users less familiar with web development terminology.
2. Clearly indicates that it's checking if a URL points to an external resource.
3. Uses "URL" which is more precise than "link" or "resource".
4. Is not overly verbose while still being descriptive.

I think isRemote is best still out of these