Update S3 Cors-Rule Subresource to Improve Diff Output

[mlivas]

When updating the allowed-origins list in an existing cors-rule for an s3-bucket, the output from Gyro appears to be entirely deleting the existing cors-rule and creating a new cors-rule with the new allowed-origins list. I expected Gyro to output that only the allowed-origins list was changing. The deletion and creation output makes it more difficult to determine if only my desired update is happening.

Based on the Gyro output, the cors rule appears to be named/idenfitied under the hood by its entire set of configurations, which likely prevents gyro from seeing that only one aspect of the configuration is changing.

Example config change:

 aws::s3-bucket "assets"
     name: "example-assets"

     cors-rule
         max-age-seconds: 3000
         allowed-headers: ["*"]
         allowed-methods: ["GET"]
         allowed-origins: [
             "https://example.com",
             "https://*.example.com",
+            "https://example2.com",
+            "https://*.example2.com"
         ]
     end
 end

Current Gyro Up output:

⟳ Update aws::s3-bucket assets (example-assets)
  · cors-rule:  -[cors-rule s3 cors rule - allowed-origins [https://example.com,https://*.example.com], allowed-methods [GET], allowed-headers [*], expose-headers [], max-age-seconds [3000]] → +[cors-rule s3 cors rule - allowed-origins [https://example.com,https://*.example.com,https://example2.com,https://*.example2.com], allowed-methods [GET], allowed-headers [*], expose-headers [], max-age-seconds [3000]]
    + Create cors-rule s3 cors rule - allowed-origins [https://example.com,https://*.example.com,https://example2.com,https://*.example2.com], allowed-methods [GET], allowed-headers [*], expose-headers [], max-age-seconds [3000]
      · allowed-headers: [ '*' ]
      · allowed-methods: [ 'GET' ]
      · allowed-origins: [ 'https://example.com', 'https://*.example.com', 'https://example2.com', 'https://*.example2.com' ]
      · max-age-seconds: 3000
    - Delete cors-rule s3 cors rule - allowed-origins [https://example.com,https://*.example.com], allowed-methods [GET], allowed-headers [*], expose-headers [], max-age-seconds [3000]

Expected Gyro Up output:

⟳ Update aws::s3-bucket assets (example-assets)
    ⟳ Update cors-rule s3 cors rule
      · allowed-headers: [ '*' ]
      · allowed-methods: [ 'GET' ]
      · allowed-origins: -[ 'https://example.com', 'https://*.example.com' ] → +[ 'https://example.com', 'https://*.example.com', 'https://example2.com', 'https://*.example2.com' ]
      · max-age-seconds: 3000