Removed self-contained scripts and added links of utilities repo scripts

[baba230896]

Original issue: Migrate to use common utilities repo instead of self contained scripts

• Issues fixed -

1. Previously yugabyte services are running by the root user. After the fix, they're running well with respective SSH Users (ec2-user). And because of this fix, we can use the same "start_master.sh" and "start_tserver.sh" scripts that we're using in terraform deployment.
2. Removed self-contained deployment scripts. And added links of utilities repo' common scripts.

• Modifications -

1. Amazon AMI ID is updated to "amzn2-ami-hvm-x86_64-gp2" from "amzn-ami-hvm-x86_64-gp2".
2. Ensure a master per zone deployment.
3. Added rpc_bind_addresses option in master.conf and tserver.conf.

The below-mentioned necessary conditions are tested with 3 nodes (1 master) and 3 nodes (3 masters) -

• crontab entries should be set to the user (ec2-user).
• ulimits configurations should be set for the user and running the yugabyte processes.
• configuration files should have rpc_bind_addresses option with correct IP.
• UI should work properly.

[iSignal]

Nice, looks good. Thanks for fixing it up to use ec2-user instead of root.

[iSignal]

One question - when we change the AMI, what happens to existing users of the cloud formation template who update to the latest version?

[baba230896]

• When I deployed the current code, I've found that using aws-cloudformation scripts we're unable to update the YugabyteDB version using the stack parameters. Then I deployed the same with previous code (without the latest changes) and found the same issue. And I think the reason for this is that whenever the update is completed we see "update completed" status on Cloudformation Dashboard whereas, in reality, the update never happened.
• Now about the AMI change, this change can break the update event on existing deployments. To overcome this, the user can use the older AMI ID.

This PR is dependent on this utilities' repo PR without these changes deployment using aws-cloudformation will fail.