fix: Configuration Updates To Setup Fresh Codebase

[shafqat-muneer]

LEARNER-9733

Description

During the initial setup of the new repository, I encountered Errors and Warnings after executing the pod install command. However, after implementing these adjustments, the repository is now free of errors and warnings. Consequently, new users can effortlessly clone the repository and install the necessary pods.

Previous error encountered:

[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod `FirebaseRemoteConfig` depends upon `FirebaseABTesting` and `FirebaseInstallations`, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

Previous warnings encountered:

[!] The `edX [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-edX/Pods-edX.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `edX [Release]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-edX/Pods-edX.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `edX [Profile]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-edX/Pods-edX.profile.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

How to test this PR

To validate this pull request, it is necessary to clone the new repository and execute the pod install command, ensuring the absence of any errors or warnings.

[saeedbashir]

As now the use_modular_headers is being used as file level, could you please remove
:modular_headers => true used for individual pods. Please do the same for edXTests target.

[shafqat-muneer]

@saeedbashir Done with suggested changes.

[saeedbashir]

I guess you need to change the use_modular_headers position or delete the comment.

[shafqat-muneer]

Done by changing the position.

[saeedbashir]

LGTM 👍