Add vPortGenerateSimulatedInterruptFromWindowsThread in MSVC port

Description

In the MSVC port of FreeRTOS, native Windows threads execute concurrently with FreeRTOS tasks and simulated interrupt handlers. Calling a FreeRTOS API from within a native Windows thread can lead to race conditions due to the concurrent execution. One way to enable synchronization between native Windows threads and FreeRTOS tasks is to make use of simulated interrupts. When a native Windows thread needs to invoke a FreeRTOS API, it generates a simulated interrupt and calls the FromISR API within the interrupt service routine (ISR).

The existing vPortGenerateSimulatedInterrupt function is designed to be called from within a FreeRTOS task, and it references the current thread structure. To facilitate calling FreeRTOS APIs from native Windows threads, this pull request introduces a new API function, vPortGenerateSimulatedInterruptFromWindowsThread. This function allows native Windows threads to generate simulated interrupts and subsequently call FreeRTOS APIs through the FromISR API, ensuring proper synchronization with FreeRTOS tasks.

Existing tick timer is an example of generating simulated interrupt from native windows thread. Another example is the cellular comm interface in this commit. Comm interface can generate simulated interrupt to notify FreeRTOS task when UART RX data is received.

In this PR

Add vPortGenerateSimulatedInterruptFromWindowsThread to enable native windows thread to synchronize with FreeRTOS task through simulated interrupt.

Test Steps

N/A

Checklist:

[X] I have tested my changes. No regression in existing tests.
[ ] ~~I have modified and/or added unit-tests to cover the code changes in this Pull Request.~~

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

FreeRTOS / FreeRTOS-Kernel