fix: populate manifestComponents consistently

[WillieRuemmele]

What does this PR do?

ensures the generated manifests are the same, when using --post/pre destructive changes or not

What issues does this PR fix or reference?

@W-17425220@

Functionality Before

would NOT error when using --post/pre when a constructive manifest had a typo
would parse out typo (as it wasn't found locally) from the manifest sent to the server, and deployment would succeed

Functionality After

will send typo to server, and allow it to error there

[shetzel]

QA
package.xml has an invalid entry (e.g., misspelled ApexClass)

sf project deploy start -x package.xml -> failed deploy as expected
sf project deploy start -x package.xml --post-destructive-changes pkg.xml -> failed deploy as expected