Update subnet sample yaml files to use subnet_secondary_ranges

[jmound]

This change is a replace of secondary_ip_range: to secondary_ip_ranges: in the code samples and tests.

The net-vpc module's data_folder gets parsed expecting the form with the "s": secondary_ip_ranges:

cloud-foundation-fabric/modules/net-vpc/subnets.tf

Line 33 in 1f71355

secondary_ip_ranges = try(v.secondary_ip_ranges, null)

Testing:

• A terraform apply using the secondary_ip_range: form causes no secondary ranges to be managed because of the try(..., null).
• Using the plural form works as intended.

[juliocc]

The test yaml files should be fine since the provider uses secondary_ip_range (without the s).

The factory files in the FAST networking stages indeed had to be fixed. Thanks for spotting this.