consistently set encoding=utf-8 for opening files

[h-vetinari]

Companion to conda-forge/conda-smithy#2244; necessary to rerender rattler recipes on windows.

[h-vetinari]

I don't know what changed in windows-land (I had thought at first that it was triggered by a local change on my machine), but this is now actually breaking CI - after a passing run, the output validation runs into:

Traceback (most recent call last):
  File "D:\Miniforge\Scripts\validate_recipe_outputs-script.py", line 10, in <module>
    sys.exit(main())
             ^^^^^^
[...]
  File "D:\Miniforge\Lib\site-packages\rattler_build_conda_compat\render.py", line 72, in parse_recipe
    yaml_content = load_yaml(recipe_path.read_text())
                             ^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\Miniforge\Lib\pathlib.py", line 1028, in read_text
    return f.read()
           ^^^^^^^^
  File "D:\Miniforge\Lib\encodings\cp1252.py", line 23, in decode
    return codecs.charmap_decode(input,self.errors,decoding_table)[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 5038: character maps to <undefined>

Please help 😅 @nichmor @wolfv

[wolfv]

Does this actually fix things? utf8 should be the default afaik since a while ...

[h-vetinari]

Nope, it'll only be the default in python 3.15 (edit: see PEP686). I've also linked a PR with CI broken due to this.

[h-vetinari]

Does this actually fix things?

Yes; I'm carrying the fixes from this PR in my local environment, otherwise I wouldn't be able to rerender the linked PR.

[wolfv]

Do you need a release then?

[h-vetinari]

Do you need a release then?

That would be great yes! For my personal use I could work around it, but it's not great that this causes CI failures (--> IMO urgent).

[nichmor]

Do you need a release then?

That would be great yes! For my personal use I could work around it, but it's not great that this causes CI failures (--> IMO urgent).

hey! let me make a release