[Feature Request] Relocate gemini-enterprise blueprint source code

## Feature Description
The `gemini-enterprise` (G4G) blueprint is currently located in the FedRAMP High-specific folder inside the `blueprints` directory, however the blueprint internally supports additional compliance regimes beyond FRH. In addition, separating out blueprints based on compliance regime increases complexity, code redundancy, and technical debt.

## Use Case
Simplifies the management and implementation of G4G deployments.

## Proposed Solution
Relocate the G4G to the top-level of the `blueprints` folder.

## Compliance & Deployment Context
* **Target Deployment Type(s):**
* [ ] US Region Restricted (e.g., Access Policy constraint)
* [ ] FedRAMP Medium
* [ ] FedRAMP High
* [ ] DoD IL4
* [ ] DoD IL5
* [x] All / General
* **Relevant NIST 800-53r5 Controls:** (If applicable, list the controls this feature helps satisfy)

## Reusability Check
Stellar Engine prioritizes reusability.
* [x] I have checked if this functionality can be achieved by extending an existing module or blueprint.
* [x] I have verified that this does not duplicate existing functionality.

## Alternatives Considered
N/A

## Additional Context
We will discuss and finalize this in our July 6 Scrum.

Locate the gemini-enterprise (G4G) blueprint inside the blueprints directory and inspect how its current FedRAMP High-specific location is referenced. Move it to the top level of blueprints so it can support all compliance regimes, then verify that the blueprint remains usable from its new location.

Written by the indexing model from the issue text.