Run `pod spec lint` on CI

[rahul-malik]

Goal

Catch issues when changes have been made to BugsnagReactNative.podspec

Design

n/a

Changeset

Update test/test-react-native-pod-build.sh to include pod spec lint BugsnagReactNative.podspec before pod install

Added

• Running pod spec lint BugsnagReactNative.podspec

Removed

N/A

Changed

• Updated `test/test-react-native-pod-build.sh

Tests

N/A

Discussion

Alternative Approaches

Outstanding Questions

Linked issues

• Remediation from the issue fixed in https://github.com/bugsnag/bugsnag-react-native/pull/453

Review

For the submitter, initial self-review:

• [x] Commented on code changes inline explain the reasoning behind the approach
• [ ] Reviewed the test cases added for completeness and possible points for discussion
• [ ] A changelog entry was added for the goal of this pull request
• [ ] Check the scope of the changeset - is everything in the diff required for the pull request?
• This pull request is ready for:
  • [ ] Initial review of the intended approach, not yet feature complete
  • [ ] Structural review of the classes, functions, and properties modified
  • [ ] Final review

For the pull request reviewer(s), this changeset has been reviewed for:

• [ ] Consistency across platforms for structures or concepts added or modified
• [ ] Consistency between the changeset and the goal stated above
• [ ] Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
• [ ] Usage friction - is the proposed change in usage cumbersome or complicated?
• [ ] Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
• [ ] Concurrency concerns - if components are accessed asynchronously, what issues will arise
• [ ] Thoroughness of added tests and any missing edge cases
• [ ] Idiomatic use of the language

[xljones]

Hey again @rahul-malik, thanks for this one too! As with #453 we'll review this one when priorities allow.

[johnkiely1]

Hi @rahul-malik,

I am closing this PR as the Bugsnag react native library has now been moved to be incorporated into the bugsnag-js repository. I have raised a new issue capturing the intention of the PR and we will update as necessary on the new issue.