[vbs-enclave-tooling-codegen] Use manual-link folder for enclave support static libs #46641
Description
Is your feature request related to a problem? Please describe.
Vcpkg auto-link static libs by default when placed in "${CURRENT_PACKAGES_DIR}/lib" for example. For C++ support in vbs enclaves we provide a static lib with stubbed out CRT functions. You can see where this is going, if you build an vbs enclave project, it will build fine. But if you build any other c++ project like a project that builds a normal Windows dll, you'll get symbol conflict errors.
Proposed solution
To fix this we should place the libs in a manual-link sub folder, like other ports do when this type of thing comes up.
Describe alternatives you've considered
No response
Additional context
No response