fix: forceignore ignores output file correctly - cleanup extra type d…

[WillieRuemmele]

forceIgnoredPaths were not getting set properly
instead of using them, instantiate a forceignore parser, and check the validated, source paths correctly

What does this PR do?

What issues does this PR fix or reference?

#forcedotcom/cli#2737, @W-15303749@ @W-15578640@

Functionality Before

adding **/Admin.profile-meta.xml in your .forceignore and running
sf project retrieve start -m Profile:Admin would output

Retrieving v60.0 metadata from test-vzakcdis7lod@example.com using the v60.0 SOAP API
Preparing retrieve request... Succeeded
 ›   Warning: Nothing retrieved

and write the file

---

**/profiles/** in .forceignore

➜ sf project deploy start -m ApexClass:FileUtilities ApexClass:PagedResult Profile:Admin
would throw an error

Functionality After

it outputs the same message, but WILL NOT WRITE the file

---

➜ sf project deploy start -m ApexClass:FileUtilities ApexClass:PagedResult Profile:Admin
will now only deploy the ApexClasses

[shetzel]

QA: both commands behave as expected with changes. Tests look good.