Restructure extension to better support multiple task versions

[rhyskoedijk]

What are you trying to achieve?

Restructure the extension so that when #1318 is reviewed, there are less changes to review.

Changes

• Moved extension\task => extension\tasks\dependabot\dependabotV1 to match the folder structure for multiple build task versions within one extension.
• Moved *.test.ts to the same directory as the file it is testing; This is going to help with clarity later where there are different tests for V1 and V2.
• Refactored build:prod script to a post dependency lifecycle script. This runs whenever npm install runs, simplifying the build steps for local development.
• Added npm start script for easier dev testing.
• Added npm run package script for easier dev testing.
• Updated extension development guide documentation.
• Reset the minor/patch version numbers in all config files, for clarity. They are automatically set in CI workflow.

Folder structure

• tasks
  • dependabot
    • dependabotV1
      • utils
        • parseConfigFile.ts
        • parseConfigFile.test.ts
        • etc...
      • task.json
      • icon.png
      • index.ts
• tests
  • config
    • dependabot.yaml
    • sample-registries.yaml

I have published the extension to DevOps and confirmed that it runs without error after these changes.

[rhyskoedijk]

@mburumaxwell it appears that each task version folder needs to be self-contained and cannot reference shared scripts from parent directories when published to a .vsix package. Because of this, some of the util scripts will need to be duplicated when V2 is added.

It seems some extension work around this issue by using build scripts to copy the shared scripts into the task directory prior to publishing. I don't have much experience with TypeScript and am unsure how to make this work whilst also correcting the module import paths, so I have not done this.

It might be something that needs to be revisited later if code duplication is a big concern.

Happy to make further changes if any of this doesn't sit well with you.

[mburumaxwell]

@mburumaxwell it appears that each task version folder needs to be self-contained and cannot reference shared scripts from parent directories when published to a .vsix package. Because of this, some of the util scripts will need to be duplicated when V2 is added.

It seems some extension work around this issue by using build scripts to copy the shared scripts into the task directory prior to publishing. I don't have much experience with TypeScript and am unsure how to make this work whilst also correcting the module import paths, so I have not done this.

It might be something that needs to be revisited later if code duplication is a big concern.

Happy to make further changes if any of this doesn't sit well with you.

Duplication is not a concern at the moment. However, we may sort it by binding using tsup sometime later.