Ability to retrieve / pull profiles with standard behavior in source tracked sandbox and scratch orgs.

[rom116]

Is your feature request related to a problem? Please describe.
Currently, in source tracked sandbox and scratch orgs, when we retrieve / pull profiles, it retrieves permissions for components in the package.xml PLUS all other components that are currently tracked.

Reference: https://developer.salesforce.com/docs/atlas.en-us.232.0.sfdx_dev.meta/sfdx_dev/sfdx_dev_source_tracking_source_tracking_profiles.htm

We would also like the option to override this behavior to retrieve/pull the "standard" way.

What are you trying to do
There are times when we want to retrieve the profile permissions for components that are ONLY listed in the package.xml or changeset from source tracked sandbox & scratch orgs.

Describe the solution you'd like
A parameter where we can override the default behavior
sfdx force:source:retrieve -x package.xml --profilestandardretrieve true
sfdx force:mdapi:retrieve -p ChangeSetName --profilestandardretrieve true

This will retrieve the profile permissions for only components that are listed in the package.xml or changeset/package.

Describe alternatives you've considered
Nothing elegant at this point.

Additional context
See Salesforce Reference Docs for current behavior in source tracked sandbox and scratch orgs.
https://developer.salesforce.com/docs/atlas.en-us.232.0.sfdx_dev.meta/sfdx_dev/sfdx_dev_source_tracking_source_tracking_profiles.htm

[github-actions]

Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments.

[uip-robot-zz]

This issue has been linked to a new work item: W-10395490

[WillieRuemmele]

Hi - we've looked into supporting profiles in that way, and found it wasn't possible without a lot of hazardous rewrites #1785 (comment)