Remove support for paging out certain functions - to simplify & fix Code Analysis warning

[forderud]

Done to simplify, so that the implementation becomes slightly easier to understand for driver "newbies". Making certain functions pageable is an optimization to reduce RAM usage that does not effect the driver functionality.

Driver binary sizes:

• Release-builds of UDEFX2.sys are 33kB on my computer.
• Release-builds of hostude.sys are 26kB on my computer.

Any RAM consumption growth is therefore guaranteed to be less than 33kb + 26kB = 59kB when both drivers are loaded. This is a negligible amount of RAM on todays computers.

I've already tested the changes with hostudetest.exe -a/hostudetest.exe -c somemission in a clean Win11 VM.

Related documentation

• Locking Pageable Code or Data - mentions #pragma alloc_text (PAGE,...)
• Writing a DriverEntry Routine - mentions #pragma alloc_text (INIT,...)

[forderud]

This PR also fixes the following warnings when running "Code Analysis" from Visual Studio:

UDEFX2\Device.c(31): warning C28170: The function 'UDEFX2CreateDevice' has been declared to be in a paged segment, but neither PAGED_CODE nor PAGED_CODE_LOCKED was found:  This warning is not emitted for functions that are __forceinline.
UDEFX_host\driver\ioctl.c(150): warning C28150: The function 'WdfSpinLockAcquire' causes the IRQ Level to be set above the maximum acceptable for the function being analyzed:  The level limits come from being PAGED_CODE or annotations on the current function.