Add Remote Gem repository workflow to Create a Gem workflow

[FuzzyCarter]

• Update Create A Gem workflow to support multiple workflows.
• Add workflow for adding a Remote Gem Repository and adding those gems to a project.
• Reformatted Workflow: Create a Gem from O3DE Project Manager to utilize a better workflow/requests/things to look for pattern.

[LB-KacperKapusta]

Workflow 1: Create a Gem from O3DE Project Manager

Workflow: Launch Create a Gem experience Steps field: 3. Select "Create a New Gem" - actual text in the Project Manager says "Create New Gem"

Workflow: Step 1 - Gem Setup Options
Encountered issues: https://github.com/o3de/o3de/issues/15541

Workflow: Step 2 - Gem Details Expectations field: "All fields can be edited" - could be "All fields can be edited:" for consistency Encountered issues: https://github.com/o3de/o3de/issues/13736, https://github.com/o3de/o3de/issues/15540

Workflow: Created Gem displays in Gem Catalog Expectations field: The "gem catalog" should be "Gem Catalog" for consistency

The Workflow has been completed with minor issues found.

Workflow 2: Add a remote gem from O3DE Project Manager

Workflow: Add Remote Gem(s) to Gem Remote Sources Manager. Encountered issues: https://github.com/o3de/o3de/issues/11159

The Workflow has been completed without major issues.

[michleza]

This looks good to me. Only 2 points things I would suggestion clarifying:

• The remote gems sample referenced at : https://github.com/o3de/sample-code-gems doesn't have an obvious sign that it's been added to a project after you've built and ran it. I'm wondering if we could put in a request or modify the same gem in some way so that it can be more easily used for testing
• The stab2305 version of project manager doesn't have a Gem in the ribbon. All I have are Projects or Engine. You can still add gems to the projects via the hamburger button but I'm not sure if I have something incorrectly configured or not

[FuzzyCarter]

@michleza

• https://github.com/o3de/sample-code-gem is only a reference example of a repository that has 3 gems (AtomTutorials, ShapeExample, PyShapeExample).
  • Aadding the depot to the gem manager doesn't add the gem to a project until after you've actually added the gem to the project (EG: AtomTutorials which will add a bunch of assets and levels to your project, ShapeExample adds a "ShapeExample" editor component entity) via Workflow: Add a remote gem from O3DE Project Manager → Add Remote Gem to an O3DE Project. → Step 2: Configure your project to add your Remote Gem(s).
  • If a tester wants to go further, they should make their own repository.
• I'm seeing the image below using the stab2305 installer, so it looks like you've got a bad local build of the O3DE Project Manager. This may also be leading to some of the issues you mentioned in your first point.

[michleza]

I think it was a bad build. I uninstalled, downloaded, and reinstalled and the Gems option is there in the ribbon now. LGTM