fix: Support specifying arrays nested in complex lists as JSON

[lgarber-akamai]

📝 Description

This change allows users to specify deeply nested array fields (e.g. --interfaces.ip_ranges) as JSON. These fields previously could not be specified at all due to limitations with how the CLI differentiates between objects in complex lists.

This PR also adds a new suffix for fields on command help pages that identifies whether an argument expects JSON.

NOTE: The failing metadata plugin unit tests are not relevant to this PR and can be ignored, see TPT-2691.

✔️ How to Test

The following test steps assume you have pulled down this change locally and run make install.

E2E Testing

make INTEGRATION_TEST_PATH=linodes/test_interfaces.py testint

Unit Testing

make testunit

Manual Testing

1. Create a VPC and VPC subnet:

export VPC_ID=$(linode-cli vpcs create --label test-vpc --region us-mia --json | jq '.[0].id')
export SUBNET_ID=$(linode-cli vpcs subnet-create --label test-subnet --ipv4 '10.0.0.0/24' ${VPC_ID} --json | jq '.[0].id')

2. Attempt to create a Linode with an interface with an explicit ip_ranges field:

linode-cli linodes create \
  --label test-instance \
  --region us-mia \
  --image linode/alpine3.19 \
  --root_pass 'testp4ssw0rd!!!!!!23123' \
  --type g6-nanode-1 \
  --interfaces.primary true --interfaces.purpose vpc --interfaces.subnet_id ${SUBNET_ID} --interfaces.ip_ranges '["10.0.0.5/32"]' \
  --interfaces.purpose=public \
  --debug

3. Ensure the ip_ranges field has been properly included in the debug output request body.
4. Navigate to the instance in Cloud Manager and ensure all fields match the creation command.

📷 Preview

Command Help Page

[zliang-akamai]

Unit test failing?

[lgarber-akamai]

Unit test failing?

@zliang-akamai The failing unit tests are related to the Metadata SSH user issue discussed last week. I think we plan on fixing that in a separate PR 👍

See: TPT-2691

[zliang-akamai]

LGTM! Local tests passed.

[yec-akamai]

LGTM! All related tests passed locally!