[patch] Fix usage of MASBR_BACKUP_DATA for mongo and db2 backup

[rawa-resul]

Description

When you export MASBR_BACKUP_DATA then it would fail the backup/restore tasks if the given value(s) are not a supported yaml file. Mongo and DB2 only support database so these should not be using MASBR_BACKUP_DATA at least until we add more features. And MAS Core and other apps should skip the value(s) in MASBR_BACKUP_DATA that are not found/supported. It's up to the user to define these values correctly.

Related issues

• mongodb community backup and restore fails when MASBR_BACKUP_DATA is exported #1492

Testing

• I ran the backup for MongoDB
• and also for IoT:

TASK [ibm.mas_devops.suite_app_backup_restore : Summary] ***********************
ok: [localhost] => {
    "msg": [
        "Job name ........................... iot-fvtcore-full-20241001153655",
        "Job status ......................... InProgress",
        "Job storage location ............... /Users/rawa/github.ibm.com/ibm-mas/ansible-devops/tmp/backups/iot-fvtcore-full-20241001153655"
    ]
}

PLAY RECAP *********************************************************************
localhost                  : ok=578  changed=75   unreachable=0    failed=0    skipped=517  rescued=0    ignored=0 

[whitfiea]

LGTM