[SM64]: HackerSM64 3.0 support

[s4Ys369]

WIP integration of new features and/or changes to allow fast64 compatibility with HackerSM64 3.0

Currently implemented:

• change how model IDs are written to model_ids.h
• Hide model ID number selection when using 3.0

[gheskett]

I would call this 3.0.0, if not just so checking patch version is more trivial/consistent if necessary

[Mushie64]

Consider setting the defaults when someone is using HackerSM64 for the following settings:
F3D Global Settings > Microcode > default from F3D to F3DEX2/LX2/ZEX
(https://github.com/Fast-64/fast64/blob/main/fast64_internal/f3d/f3d_material.py#L4988)

SM64 General Settings > SM64 Repo Settings > Compression Format > default from MIO0 to YAY0
(https://github.com/Fast-64/fast64/blob/main/fast64_internal/sm64/settings/properties.py#L73)

...or otherwise handle the defaults sensibly to match the ones from the current repo using HackerSM64.
Adding this comment as a decomp beginner who used the supposedly default settings for basically everything and got this (image below) on my first attempt before asking for help. I heard that "this seems to be a fairly common issue among decomp beginners", which I didn't expect to be the case.

[s4Ys369]

An update fast64.json with these appropriate settings has been included in hacker as of September HackerN64/HackerSM64@27fedee#diff-4e8d2fc8659d21b104963768ed18776f39ad006af57450eb2530ebe0dc8c4063

[Mushie64]

Yeah, after my post yesterday I was told of the fast64.json file too. On my end it looks like it does in the github repo, which I expect means the problem is instead "it didn't get read by Blender". It might be a case of "didn't work on my machine". Should I open an issue about it, here or at HackerSM64?
(Also, should I delete my previous comment? It doesn't sound all too helpful in hindsight.)