Revert "Encode the style URL in iOS (#2965)"

[louwers]

This reverts commit d140d5e.

This commit has caused several regressions #3023

Potentially also #2993

I want to revert it, put out a release, and then look for a fix.

[HarelM]

I would advise to split a revert PR with a version release PR, but that might be an overkill.
I think it helps to see in the git history a commit for "bump version" (besides the tagging of course) since then you can easily see which commit was added in which version without a lot of hassle.
I use an action to create a bump version PR, which also takes care of the change log modification. I think it's a nice way to solve this, also it allows me to release a version without any extra approval (which is nice by its own).

[louwers]

@HarelM I agree that is a cleaner way to do it. I am guilty of lumping unrelated things into one PR, because CI for this repo is quite heavy and takes a long time to run. Not really a good reason though.

I usually update the changelog as part of the version bump PR. I also think that releasing a version should require an approval.

[github-actions]

Bloaty Results (iOS) 🐋

Compared to main

    FILE SIZE        VM SIZE    
 --------------  -------------- 
  -0.0%    -144  [ = ]       0    TOTAL

Full report: https://maplibre-native.s3.eu-central-1.amazonaws.com/bloaty-results-ios/pr-3024-compared-to-main.txt

[HarelM]

If all you do is "push the release button" I don't see a lot of merit in approving this. But I guess it also depends on how fast you get a PR approval for something so trivial, which I find to long in my case...