Add Fault Injection in WFP OS APIs

[shpalani]

Description

• Added fault injection condition in the following WFP OS APIs:

1. FwpmFilterDeleteById0
2. FwpmTransactionBegin0
3. FwpmFilterAdd0
4. FwpmTransactionAbort0
5. FwpsCalloutRegister3
6. FwpmCalloutAdd0
7. FwpsCalloutUnregisterById0
8. FwpmEngineOpen0
9. FwpmProviderAdd0
10. FwpmSubLayerAdd0
11. FwpmEngineClose0
12. FwpsInjectionHandleCreate0
13. FwpsInjectionHandleDestroy0

• In net_ebpf_extension_initialize_wfp_components(), added a call to close the session and to unregister the callouts for the failure paths.

• Fixed an issue in net_ebpf_extension_initialize_wfp_components(), where the failure status was overwritten with FwpmTransactionAbort() return value and returned as success to the caller. This led the code flow to continue with the assumption that the initialization of wfp components (ie, registering callouts and adding callouts) was successful... This caused assert failure during NmrClientAttachProvider flow.

Exit:
   if (!NT_SUCCESS(status)) {  <<< original failed status
        if (is_in_transaction) {
            status = FwpmTransactionAbort(_fwp_engine_handle);   <<<< overwritten
       ...
   }
   NET_EBPF_EXT_RETURN_NTSTATUS(status);   <<<<< return with overwritten value

• Added traces for some failures.

Note: This is an incremental commit. There are 11 more WFP APIs pending in fwp_um.cpp. Please see #2101 for details.

Testing

_Do any existing tests cover this change? Yes
Are new tests needed? No

Existing test cases with fault injection call stack of 4:
unit_tests.exe: PASSED
netebpfext_unit.exe: PASSED

Documentation

_Is there any documentation impact for this change? No

[dthaler]

@shpalani rebase to pick up scorecards fix