Create Child recipe for UMS supported on OLM to fusion BR process

[YCShen1010]

What this PR does / why we need it:
Add backup and restore support for IBM Usage Metering Service resources on OLM in fusion by creating a child recipe and intergrating it with the parent CPFS recipe

Which issue(s) this PR fixes:
Fixes # https://github.ibm.com/IBMPrivateCloud/roadmap/issues/67328

[YCShen1010]

backup passed:

[YCShen1010]

Restore passed:

[YCShen1010]

Install UMS procedure:

1. Create OperandRequest for UMS

apiVersion: operator.ibm.com/v1alpha1
kind: OperandRequest
metadata:
  name: example-service
spec:
  requests:
    - operands:
        - name: ibm-usage-metering-operator
      registry: common-service

2. Create an example of Metering Definition CR (ref: https://pages.github.ibm.com/IBMPrivateCloud/BedrockServices/AdopterGuides/UsageMeteringService.html#registration-cr-example)

apiVersion: operator.ibm.com/v1
kind: IBMServiceMeterDefinition
metadata:
  name: test-metering-definition
  namespace: <UMS namespace>
spec:
  data:
    instanceId: 0000111122223333aaaabbbbccccdddd
    metricDescription: Number of resource units consumed
    metricName: RESOURCE_UNIT
    metricType: CONTRACTUAL
    productId: 8c29d5c88ec5489b929bea924cc1eabf
    productName: CloudPak for Data Enterprise Edition
  mappingId: 0123abcd0123abcd0123abcd0123abcd
  processing: ADD

[bluzarraga]

My restore test keeps failing because of this error from velero:

{"level":"error","logSource":"pkg/restore/restore.go:1651","msg":"error restoring data-lineage-metering-definition-for-ru: IBMServiceMeterDefinition.operator.ibm.com "data-lineage-metering-definition-for-ru" is invalid: spec.mappingId: Required value","restore":"ibm-bnr/backup-resources-a8b7e142-1a46-437e-93e8-446b64fc8cb5","time":"2025-09-12T21:32:23Z"}

Maybe its something with how I setup my cluster but I think I am going to have to try again next week

[bluzarraga]

I tried it again today and I still get the same error but only for two of the four service meter definitions. I checked the beta doc (which is what I used to create these crs) and this tracks that two of them do not contain the field that is being complained about. I am not sure if maybe this doc is outdated and these crs should have the mappingid field or if somehow oadp does not like it? I will try to ask licensing team to see if this is something we should be concerned about. Otherwise the BR is working as expected so I don't want to hold this up unnecesarily

[bluzarraga]

confirmed with Kacper from licensing that I was using an older version. Later versions of ums have spec.mappingid as a not required field. With that said I will approve this

[bluzarraga]

/lgtm

[ibm-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bluzarraga, YCShen1010

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [YCShen1010,bluzarraga]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment