Fix Data Node Splitting in Tiers

[jcalfayan]

Description of changes:

• This PR fixes the problem that currently splitting the middleManager and historicals into separate tiers only works if both your Tier 1 and Tier 2 nodes have the same name.
  • For example:
    • Tier 1: data | Tier 2: data_tier2 👍
    • Tier 1: data | Tier 2: middleManager_tier2, historical_tier2 👎 (expected to work)
    • Tier 1: middleManager, historical | Tier 2: middleManager_tier2, historical_tier2 👍
    • Tier 1: middleManager, historical | Tier 2: data_tier2 👎 (expected to work)
• The reason is that currently when we get the instance type information we expect the props.nodeType to exist which in the case of both tiers having the same node type, it will, otherwise it will not which will cause the deploy to fail since we will not be able to grab the AWS resource information since we will set the parameter to utils.getInstanceTypeInfo as an empty string.

[bios6]

Thank you for your PR. We are working on incorporating this change on the v1.0.5 release

[bios6]

This change was added into release v1.0.5 . Thanks!