`meson init` with source or executable arguments broken since 1.8.0

[thesamesam]

Describe the bug

meson init --lang c --executable gm doesn't seem to honour the executable name, nor discovered source files.

$ git bisect good 1.7.0
$ git bisect bad 1.8.0
[...]
$ git bisect skip
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
1b14526243c3e12c132ee8f81089fea0425bab7d
19cf54418553d835ec1de4d8a919a442545c0272
b94cbbfb79eaeaf863d77fca1dd051b102471ad3
484ac23b512f2ccc008ad9b9520016fbaa3645f0
b3d1b7af0707da946701f986e86c6e5421ae84e8
55e3a5ece5d90ea29dcb8ab2d0bb6898a71e8971
68939da3bd33096f1f01e67ecd2f8ff1ee84a4d9
9f0ac314ba0c54cc18c2499845324efc14c1849e

To Reproduce

$ git clone https://codeberg.org/amonakov/guildmaster
$ git checkout f63b2b6ab8dcd1bc37c7311ca835d8dc1f0c7958
$ ~/git/meson/meson.py init --language c --executable gm --force -b # successfully builds dummy 'guildmaster' when it should fail with discovered source files, building an executable 'gm'

Expected behavior

• The --executable parameter to be honoured
• Either discovered source files to be used in meson.build or for the message to not be emitted

[thesamesam]

I'm poking more now.

[thesamesam]

Since 9f0ac31, we don't look at srcfiles which minit populates at all.

cc @dcbaker