Plan of porting over some features from PowerShell Pro Tools extension

[kilasuit]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been reported.

Summary

Now that the PowerShell Pro Tools extension by @adamdriscoll extension has been open-sourced it may make sense to look at migrating many, if not all, of the features across to this extension as to provide the best experience in the future

This issue is to discuss whether this is the direction we want to go and if so what parts could be migrated in to this repo along with in future a potential time-frame for this & follows on from this comment from that @JustinGrote raised in the Pro Tools Repo

Proposed Design

No response

[ArieHein]

Definitely a module and command window based on Get-Module -ListAvailable so it will show you where the modules come from, what commands each module has, has it been added with a prefix, the ability to filter by module name or function names across modules (potential pointing to issues that required us to use Clobber at the past that we forgot about, when were trying to debug why a specific function isn't behaving the way it should)