Fixed iOS framework compilation warnings

- Fixed or disabled some warnings produced by clang compiler during iOS frameworks build.
- Extracted same block from some cmake scripts (add_apple_compiler_options).
- Updated `platform/ios/build_framework.py` script to break the build in case of error in cmake or xcodebuild steps. This change allows buildbot to handle these cases better.

In clang's `arm_neon.h` these methods are declared using macros:
```
#define vshlq_n_s32(a, __b) __extension__ ({ \
  int32x4_t __a = (a); \
  (int32x4_t)__builtin_neon_vshlq_n_v((int8x16_t)__a, __b, 18); })

#define vshrq_n_s32(a, __b) __extension__ ({ \
  int32x4_t __a = (a); \
  (int32x4_t)__builtin_neon_vshrq_n_v((int8x16_t)__a, __b, 18); })
```
And we get compiler warning:
```
warning: declaration shadows a local variable [-Wshadow]
            int32x4_t v_dst0 = vshrq_n_s32(vaddq_s32(vqaddq_s32(v_r00, vshlq_n_s32(v_r10, 2)), v_delta), 8);
                                                                       ^
note: expanded from macro 'vshlq_n_s32'
  int32x4_t __a = (a); \
            ^
note: expanded from macro 'vshrq_n_s32'
  int32x4_t __a = (a); \
                   ^
```
... and GCC uses inline methods for this. I've compared execution time of some of `opencv_test_imgproc` shards on [build 133](http://pullrequest.opencv.org/buildbot/builders/precommit_arm/builds/133) and [build 134](http://pullrequest.opencv.org/buildbot/builders/precommit_arm/builds/134), it is same.