fix: support adding and removing Localizable.strings file

[OmarIthawi]

XCode project supports adding Localizable.strings file in multiple variants in which each language gets its own variant with the language code as the file "name" property.

Before

• The file would be added under incorrect Resources section
• The file ID would still be referenced in the Localizable.strings PBXVariantGroup section event though it has been removed
• File cannot have a custom name

After

• The file can be added to the correct group via the parent parameter in ProjectFiles.add_file() method
• When a file is removed, it's references are removed from both PBXGroup and PBXVariant group sections
• Files can have custom names, differing from its path
• More fixes for the productRef issue

TODO

• [x] Fix broken tests
• [ ] Add new tests for the changes

Fun fact

This code is written on Linux, with help from my colleagues to debug the version once it's ready on their iOS devices.

Thanks!

This project has been very helpful for us in openedx/openedx-app-ios. Thanks for creating it and double thanks for your fast triage for the other pull request.

[OmarIthawi]

@kronenthaler Thanks for the help on the other pull request. Would you mind enabling tests for "Second time contributors" like myself?

This can be done by selecting the "Require approval for first-time contributors" option as explained here:

• https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks

[OmarIthawi]

Thanks @kronenthaler! I would appreciate a quick review before I go on and add tests for the new features I've built.

I really appreciate your help! I'm working on another opensource project and your help by both providing this project and traging pull requests has been remarkable.

[OmarIthawi]

@kronenthaler Would you mind sharing an update on how do we think we should proceed with this pull request?

[kronenthaler]

@kronenthaler Would you mind sharing an update on how do we think we should proceed with this pull request?

I will take a look somewhere this week and advise how to proceed.