fix: prevent incorrect scheme addition in URL parsing

[rjvkn]

Description

This PR resolves an issue in the tldify.Parse function where URLs with either the http:// or https:// scheme were incorrectly being parsed with an additional scheme. The problem occurred because the function was always prepending http://, even when the URL already had one of these schemes.

Changes

• The logic in Parse was modified to check whether the URL already starts with http:// or https:// before prepending any scheme.

Motivation and Context

This change prevents incorrect scheme duplication and ensures that URLs like https://example.com are handled correctly.

How to Test

You can test this fix by passing URLs like https://example.com and checking that the function does not prepend http:// again. Any URLs without a scheme should receive http:// as expected.

Screenshots (if applicable)

Checklist

• I have read the contributing guidelines.
• My code follows the code style of this project.
• I have tested my change.