Fix #998 - Resolved parameter properties by TMP.

[samchon]

When declare a class type with public parameter properties, and the class type has some private member variables too, the public parameter properties had not identified by typia when the class type casted to a pritmitive object type through TMP type like Primitive or Resolved.

It was because TypeScript compiler API still consider the public members as parameter properties even when converted to the primitive object type through TMP (type meta programming) like Resolved<T>. Ths PR fixes the bug, by considering the special case of the TypeScript compiler API, so that same bug would not be occured more.

For reference, if there's not any private members or no parameter properties being utilized in a class type, no error be occured. This is the extremely rare case I hadn't known. Thanks for @hambergerpls to reporting such special case.

class Foo1 {
  private _y: string;
  constructor(public readonly x: string) {
    this._y = "y";
  }
}
const foo: Foo1 = new Foo1("x");
const cloned: Resolved<Foo1> = typia.misc.clone(foo);

// it came error because `typia` could not identify
// the pritmive type cased parameter propertized class type
// through TMP (type meta programming)
typia.assertEquals(cloned);