fix(ios): start initial timer id from one

[janvennemann]

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

Optional Description:
We use simple number values as timer identifiers, which used to start from 0. This could cause unexpected behavior when checking for a timer id since it evaluates to a falsy value for the first timer. Always starting and incrementing the timer ids from 1 solves the issue.

[build]

	Fails
🚫	Test suite crashed on iOS simulator. Please see the crash log for more details.

	Messages
📖	✊ The commits in this PR match our conventions! Feel free to Rebase and Merge this PR when ready.
📖	✅ All tests are passing Nice one! All 4388 tests are passing. (There are 472 skipped tests not included in that total)

Generated by 🚫 dangerJS against 57bca56

[vijaysingh-axway]

CR passed.

[vijaysingh-axway]

@janvennemann Is it possible to add unit test for this? I think it can be achieved by appending the log message in a string and compare it after completion.

[janvennemann]

@vijaysingh-axway I thought about that, but the issue is actually pretty hard to test with our test suite. This issue only occurs for the very first timer started after the app launched. However, we use timers all over the place so i don't even get a chance to test for this particular bug.