Sm/coft-deploy-fix

[mshanemc]

What does this PR do?

makes it possible to deploy just a CustomObjectFieldTranslation (decomposed child of customObjectTranslation)

Background:
COFT is not in the metadata api--it has to be rolled up into a COT to be deployed.
The following would not work:

1. force:source:deploy -p [path to COFT]
2. changing a COFT file locally and calling force:source:push

This now:

1. will resolve a CFT to its parent COFT when building componentSets
2. when a COT is deployed, will create FileReponses for each of the child CFT (we don't know which ones were deployed, so we mark them all. These fileResponses also make sure that source tracking updates correctly for CFT)

What issues does this PR fix or reference?

@W-11811429@

[WillieRuemmele]

QA Notes:

---

setup

with a project with COFT

---

✅ deploy -p force/app
✅ deploy -p force-app/main/default/objectTranslations
✅ deploy -p force-app/main/default/objectTranslations/customObject__c-es/customField__c.fieldTranslation-meta.xm
✅ deploy -p force-app/main/default/objectTranslations/customObject__c-es/customObject__c-es.objectTranslation-meta.xml
✅ : retrieve -p force-app/main/default/objectTranslations
❓ :

retrieve -p force-app/main/default/objectTranslations/customObject__c-es/customField__c.fieldTranslation-meta.xml 
Preparing retrieve request... done
=== Retrieved Source

No results found

✅ retrieve -p force-app/main/default/objectTranslations/customObject__c-es/customObject__c-es.objectTranslation-meta.xml