Enhance documentation clarity for JSON field inputs for the ECS work pool and ideally across other work pool types

[taylor-curran]

First check

• I added a descriptive title to this issue.
• I used GitHub search to find a similar request and didn't find it 😇

Describe the issue

When a user goes in to add network connection information to their ECS worker, the UX is like:

When they click on the link to aws docs they are given the following JSON example:

{
  "AssignPublicIp" : String,
  "SecurityGroups" : [ String, ... ],
  "Subnets" : [ String, ... ]
}

^Notice a capital S for Subnets.

However, further research into AWS docs led me to

If you are defining ECS services in a CloudFormation template, use "Subnets". If you are using the Boto3 client, use "subnets".

With respect to the Prefect ECS work pool, we employ boto3. The request that is happening under the hood is RunTask, so a lowercase s is used.

  "networkConfiguration": { 
     "awsvpcConfiguration": { 
        "assignPublicIp": "string",
        "securityGroups": [ "string" ],
        "subnets": [ "string" ]
     }
  },

The following worked for the user after extensive trial and error:

{"awsvpcConfiguration":{"subnets":["subnet-xx","subnet-xx"],"assignPublicIp":"DISABLED"}}

While adding the following addition to the base job template:

      "launchType": "{{ launch_type }}",
      "taskDefinition": "{{ task_definition_arn }}",
      "networkConfiguration": "{{ network_configuration }}"

Describe the proposed change

Ideally the in-UI and external documentation makes it clearer what should be included in each text/JSON block. We recommend enhancing documentation clarity for JSON field inputs across all work pool types by providing precise examples that reflect the required API or framework and aligning field names with their actual API counterparts, ensuring correct casing and format. This will help ensure accuracy and improve user experience.

Additional context

No response