test(nostr): unit test Blossom.buildServerListTags

[NicolaLS]

noticed a quality issue here:

wisp/app/src/main/kotlin/com/wisp/app/viewmodel/BlossomServersViewModel.kt

Lines 47 to 64 in 56c26c2

	fun addServer() {
	val raw = _newServerUrl.value.trim().trimEnd('/')
	if (raw.isBlank()) return
	if (raw.startsWith("http://")) {
	_error.value = "Only HTTPS servers are supported"
	return
	}
	val url = if (raw.startsWith("https://")) raw else "https://$raw"
	val current = servers.value.toMutableList()
	if (current.contains(url)) {
	_error.value = "Server already added"
	return
	}
	current.add(url)
	blossomRepo.saveBlossomServers(current)
	_newServerUrl.value = ""
	_error.value = null
	}

this function allows lots of bad stuff eg.

• example com -> https://example com
• HTTPS://example.com -> https://HTTPS://example.com
• ftp://example.com -> https://ftp://example.com

Also allows fragments (#) and query parameters (?) in url that can be an issue when appending /media in the repository. It should be defined whether we allow something like https://example.com?query=a#fragment and then append /media like this https://example.com/media?query=a#fragment or just don't allow it.

Correct validation logic should be used for user input as well as when parsing kind 10063 events.

[NicolaLS]

I guess pointing out the validation problem in this PR is not optimal but I noticed it when implementing these unit tests as I decided not to add url validation to the builder method because that would be unnecessary overhead, its quite far away from the UI/wire and should not own validation which is why I checked whether the components that do own it do it properly.