Add base repository and interface from template if the user accepts the pattern when adding prisma provider

[juliano-soares]

Problem:

The current process of setting up the Prisma provider lacks the option to include base repository classes and interfaces as part of the scaffolded codebase. Providing this feature would streamline the project structure and ensure consistency across repositories.

Proposed Solution:

When executing the command to add the Prisma provider, prompt the user with a question about whether they'd like to include the base repository classes and interfaces in the scaffolded codebase. If the user agrees, the existing base repositories should be replaced with those specific to the Prisma provider. It's crucial to inform the user that accepting this replacement will result in the removal of existing files.

Note: The base repository and interface examples are already in the following CLI branch: ETS-269-Add-the-CLI-to-scaffold-the-service

Implementation:

• Modify the CLI command for adding the Prisma provider to include a prompt regarding the inclusion of base repositories and interfaces.
• If the user agrees, replace the existing base repository and interface files with the Prisma-specific versions.
• Provide a clear warning to the user about the potential removal of existing files due to the replacement.
• Update the documentation to explain the new feature and its implications.