fix(amplify-frontend-ios): encapsulate path option values with quotes

[josefaidt]

Description of changes

adds quotes to --path option values to prevent breaking when absolute path to amplify project contains spaces

Issue #, if available

fixes #12593

Description of how you validated changes

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)
• New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
• Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[aws-eddy]

LGTM

[Amplifiyer]

can we add unit tests to validate the pre & post behavior

[josefaidt]

Hey @Amplifiyer what do you mean by pre and post behavior?

[MorFix]

@josefaidt Is there a chance that this broke code generation for iOS?

Our team now getting this after amplify pull (after models are already generated):

Updating Xcode project:
🚫 folderNotFound: Amplify project not found at "/Users/<USER>/GitHub/<PROJECT>".
-- Recovery suggestion: Run `amplify init` to initialize an Amplify project.
🛑 Command failed with exit code 1: /Users/<USER>/.amplify/lib/aws-amplify-amplify-frontend-ios/resources/amplify-xcode import-config --path="/Users/<USER>/GitHub/<PROJECT>"

Reverting this commit either by a local amplify-dev or by downgrading to 12.2.3 solves this.
I don't mind contributing a fix to this (I guess it's in amplify-xcode) and tests if I can have the amplify-xcode source :)