UX for "Make Code" is a little under-baked

[emesare]

The title is generic as these two issues can be tackled together IMO.

1. Make code will not prompt the user to select a platform if for example you open a new file with no platform
   • Open a new file paste raw hex: 8b0df00e4200a1000f42003bc872028bc8506a6451ff1548814000c3
   • Make code (keybind is C) at 0x0
   • Observe data variable BN_CODE_start_0x0_size_0x1c

Screen.Recording.2025-01-20.at.3.17.05.PM.mov

2. Make code does not show the opcode bytes:

[xusheng6]

Blocked on #5513 -- until this is resolved, we have no way to provide the disassembly setting to the data renderer

[psifertex]

semi-related #5523

[xusheng6]

The tentative solution for this is we need to revamp how "make code" works. Basically, the idea is that we will still create a function object for it, but there will be metadata for it so that:

1. When the function gets disassembled, it only gets disassembled for the first basic block
2. In addition to 1), we could also limit it to maybe a max of 50 instructions
3. We do not generate the IL for the function

Some of this might coincide with how "guided disassembly" works as well

I believe this is better because it also solves issues like comment, highlight, etc