Add support to scaffold devcontainer

[tanwigeetika1618]

JIRA ticket: https://issues.redhat.com/browse/AAP-32979

Description

• Implemented Scaffolding for devcontainer Resource Type:
  • Updated add.py to include template data handling for the devcontainer resource type.
  • Modified arg_parser.py to support the devcontainer resource type alongside existing types like devfile and role.

Changes

• add.py:

  • Added logic to handle devcontainer resource type scaffolding.
  • Integrated template_data for both devfile and devcontainer to ensure proper templating during the scaffolding process.
  • Enhanced the _scaffold method to include conditions for devcontainer.

• arg_parser.py:

  • Updated argument parsing to include devcontainer as a valid resource-type.
  • Ensured that optional arguments are appropriately handled for the new resource type.

• Testing and Validation:

  1. Successful Scaffolding: Update unit tests to cover scenarios involving the scaffolding process for devcontainer to ensure that all necessary files and directories are correctly copied to the destination path.
  2. Overwrite Scenario: Modifies the .devcontainer content and checks the behavior of the overwrite parameter, ensuring that conflicts are handled appropriately during scaffolding.

Summary:
This update provides the initial scaffolding capability for devcontainer resources to the destination path provided.

[audgirka]

@cidrblock When scaffolded this uses the community-ansible-devtools image.
What would happen in the downstream environment scenario when the devcontainer file is scaffolded?
Will it use a downstream image or do we need to provide the image name as part of TemplateData instance creation?

[audgirka]

@ssbarnea any thoughts on this?

[audgirka]

@tanwigeetika1618 Per discussion with @cidrblock, for now we can add a downstream image option which will be commented by default while scaffolding the devcontainer files.
Will need a jira and more discussion on adding another cli option.
@ssbarnea ^^