Migrate terraform module from bcgov-c to Github entreprise

**Describe the Issue**
The way terragrunt works require valid access to both private and public repository.
We are encountering issues because of the way git credential works because it can only have one https access and one ssh.

To resolve our issue we need to migrate all the Terraform module from BCGov-c to Github entreprise.

**Additional Context**
- All the terraform public git repo will be access though https
- All the entrerpise git repo will be access through SSH from the terragrunt source with a key configured
- - terraform-aws-ecf-automation-setup
- - terraform-aws-keycloak-ecf-roles-setup
- - terraform-aws-keycloak-ecf-role-sync

**Acceptance Criteria**
- All the BCGov-c git repo has been migrated to Git BCGOV Entreprise
- All the source in terragrunt file will be migrate to point toward the new location of the module.
- The workspaces sources will be configured as metion in additionnal context above

.
.
.
.
.
.
.
.
.
.
.

**Extra Template Info**

***Definition of Ready***
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.

***Acceptance Criteria***
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for
- managing expectations
- defining scope
- reducing ambiguity
- establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

***Definition of Done***
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.
- Documented = Captured in Community Update (CU) deck
- Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

Start by locating the terragrunt files and workspace source configuration that reference BCGov-c modules. Review the listed modules—terraform-aws-ecf-automation-setup, terraform-aws-keycloak-ecf-roles-setup, and terraform-aws-keycloak-ecf-role-sync—and verify the required HTTPS and SSH access paths. Done means the repositories are migrated to GitHub Enterprise, all references use the new locations, and workspace sources follow the stated configuration.

Written by the indexing model from the issue text.