fix(ios): properly inject CODE_SIGN_IDENTITY flag for Xcode 11 compatibility

[hansemannn]

JIRA: https://jira.appcelerator.org/browse/TIMOB-27330

Requires tidev/ioslib#91 + package.json update to 1.7.11 once merged.

[build]

	Messages
📖	💾 Here's the generated SDK zipfile.
📖	🎉 Another contribution from our awesome community member, hansemannn! Thanks again for helping us make Titanium SDK better. 👍
📖	✅ All tests are passing Nice one! All 4342 tests are passing. (There are 472 tests skipped)
📖	✊ The commits in this PR match our conventions! Feel free to Rebase and Merge this PR when ready.

Dependencies with modified semantic versioning:

• ioslib - from ^1.7.10 to ^1.7.11

Generated by 🚫 dangerJS against c16f49d

[hansemannn]

Using the old certificates fixed it for me. Although I'd still argue that we should properly assign certs directly instead of gambling that Xcode does it for us in the future.

Also, still not supporting automatic code signing these days is really bad and will cause more and more issues in the future as developers move to generating their certs automatically.

[cb1kenobi]

@hansemannn We used to explicitly set the certificate, but then I believe we went to the generic "iPhone Developer" when we added Apple Watch support. We mix the watch app targets into the Titanium app's Xcode project and wire up the target dependencies and I believe that there were issues signing the watch apps and the iOS app when using an explicit cert.

I'm not opposed to looking at it again, we just need to remember to test watch apps. :)

+1 for the "Apple Developer" cert support.

[hansemannn]

Makes sense. Can you remove the milestone? Then we should be fine :)