Yes, as you note, I was half way through updating the wiki from talking about fixes 2.2 to fixes 3.0 but principles still apply. Sorry !
My test run was on Intel Monteray, I don't have a Apple Silicon box but, apart from where noted, I'd expect it to be the same (But, honestly, knowing how Apple work, would not be surprised if it was not.).
From what I have seen, MacOS seems happy to ignore capitalization when it suits itself. Crazy, should be either case sensitive or not.
It sounds like Graham is building from source so no need to use startlazarus, but one more problem I should have mentioned. If you start Lazarus from the Finder, by double clicking on the lazarus.app bundle (or, I think, the startlazarus.app bundle) it does not look at your lazarus.cfg file, that says to me its not starting it in the main lazarus directory, that could mean a relative path to the config dir won't work. Just speculation.
A solution, at least as a test, would be to open Lazarus from the command line.
$> cd some-lazarus-dir <enter>
$> open lazarus.app <enter>
Next suggestion is to try and capture the console output from Lazarus, not that easy on MacOS, needs to be sent to a file with a command line switch.
open start.app --args "--debug-log=Set-some-absolutepath-to-writeable-file" <enter>
Davo