Add support for TypeScript with 'none' for module config

[erikolofsson]

Importing through "." engages the module machinery in TypeScript so it's not possible to import the types into a project with None module resolution.

Example import:

import * as ImportScim2ParseFilter from "../../node_modules/scim2-parse-filter/lib/src/index";

declare global {
	namespace Scim2ParseFilter {
		export type Filter = ImportScim2ParseFilter.Filter;
	}
	export type Scim2ParseFilter = typeof ImportScim2ParseFilter;
	const Scim2ParseFilter: Scim2ParseFilter;
}

export {};

Results in:

.../node_modules/scim2-parse-filter/lib/src/stringify.d.ts:1:24: Error TS2792: Cannot find module '.'. Did you mean to set the 'moduleResolution' option to 'nodenext', or to add aliases to the
   'paths' option?

This is fixed by importing explicitly from "./index" instead.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[thomaspoignant]

Hey @erikolofsson, sorry for the time it took me to review this.
I was super busy on other projects, but this is great, thanks a lot for your contribution 🙏