Google Cloud SQL commitment prices are not listed correctly

[aliscott]

For Google Cloud SQL the 1 year and 3 year commitment prices are not listed correctly in the Google Billing Catalog API.

Example:

    {
      "name": "services/9662-B51E-5089/skus/8AA4-4E86-978A",
      "skuId": "8AA4-4E86-978A",
      "description": "Commitment - dollar based v1: Cloud SQL database us-east1 for 1 year",
      "category": {
        "serviceDisplayName": "Cloud SQL",
        "resourceFamily": "ApplicationServices",
        "resourceGroup": "SQLGen1Instances",
        "usageType": "OnDemand"
      },
      "serviceRegions": [
        "us-east1"
      ],
      "pricingInfo": [
        {
          "summary": "",
          "pricingExpression": {
            "usageUnit": "h",
            "usageUnitDescription": "hour",
            "baseUnit": "s",
            "baseUnitDescription": "second",
            "baseUnitConversionFactor": 3600,
            "displayQuantity": 1,
            "tieredRates": [
              {
                "startUsageAmount": 0,
                "unitPrice": {
                  "currencyCode": "USD",
                  "units": "0",
                  "nanos": 7500000
                }
              }
            ]
          },
          "currencyConversionRate": 1,
          "effectiveTime": "2021-03-31T13:45:49.814Z"
        }
      ],
      "serviceProviderName": "Google",
      "geoTaxonomy": {
        "type": "REGIONAL",
        "regions": [
          "us-east1"
        ]
      }
    },

We parse these prices as $0.0075, but really the commitment price is 0.75 * the on-demand price.

For Google Compute Instance resources the commitment prices are listed as the actual hourly price of the resource given the commitment. We would expect the Cloud SQL prices to be similar.