The warnings from 3rd-party code can mostly be ignored, because it is not
under the control of our team. In Xcode, this allows us to focus on
the issues that we are able to fix.

Since all warnings are inhibited by default, there is no need to
manually set this parameter here to `true`.

As requested by @pixlwave during their review of #6196, these
`inhibit_warnings` directive configure CocoaPods in a way that the
warnings for both MatrixSDK and AnalyticsEvents show up when building
the workspace in Xcode.

…Inhibit-all-warnings-from-pods