Refactor IBMiComponent for easier export

[worksofliam]

Refactor methods in the IBMiComponent class to improve export functionality. This includes changing access modifiers and return types for better clarity and consistency.

It also enables IBMiComponent to be implemented, and not only extended. This is particularly important for other extensions, so they can add their own components.

  class a implements IBMiComponent {
    state: ComponentState = `NotChecked`;
    cachedInstallDirectory: string | undefined;
    constructor(readonly connection: IBMi) {}
    async getInstallDirectory(): Promise<string> {
      return `BOOP`;
    }
    getState(): ComponentState {
      return `NotInstalled`;
    }
    async check(): Promise<ComponentState> {
      return `NotInstalled`;
    }
    toString(): string {
      throw new Error("Method not implemented.");
    }
    getIdentification(): ComponentIdentification {
      return {name: `test`, version: 1};
    }
    getRemoteState(): ComponentState | Promise<ComponentState> {
      throw new Error("Method not implemented.");
    }
    async update(): Promise<ComponentState> {
      return `Installed`;
    }
  }
  
  extensionComponentRegistry.registerComponent(context, a);

[github-actions]

👋 A new build is available for this PR based on f0618d3.

• Download here.
• Read more about how to test

[worksofliam]

This screenshot shows that with this PR, we can implement the IBMiComponent to add components.