Fix compiler bug with nested optional arguments

This commit fixes compiler bug where it fails when optional values are
compiled into absent values in nested calls.

- Throw exception with more context for easier future debugging.
- Add better validation of argument values for nested calls.
- Refactor `FunctionCallCompiler` for better clarity and modularize it
  to make it more maintainable and testable.
- Refactor related interface to not have `I` prefix, and
  function/variable names for better clarity.

Context:

Discovered this issue while attempting to call
`RunInlineCodeAsTrustedInstaller` which in turn invokes `RunPowerShell`
for issue #246. This led to the realization that despite parameters
flagged as optional, the nested argument compilation didn't support
them.

tests/unit/shared/Stubs/SharedFunctionCollectionStub.ts

@@ -5,7 +5,7 @@ import { SharedFunctionStub } from './SharedFunctionStub';
 export class SharedFunctionCollectionStub implements ISharedFunctionCollection {
   private readonly functions = new Map<string, ISharedFunction>();
 
-  public withFunction(...funcs: readonly ISharedFunction[]) {
+  public withFunctions(...funcs: readonly ISharedFunction[]): this {
     for (const func of funcs) {
       this.functions.set(func.name, func);
     }
@@ -21,4 +21,12 @@ export class SharedFunctionCollectionStub implements ISharedFunctionCollection {
       .withCode('code by SharedFunctionCollectionStub')
       .withRevertCode('revert-code by SharedFunctionCollectionStub');
   }
+
+  public getRequiredParameterNames(functionName: string): string[] {
+    return this.getFunctionByName(functionName)
+      .parameters
+      .all
+      .filter((p) => !p.isOptional)
+      .map((p) => p.name);
+  }
 }