update install manifest for aeraki

[tanjunchen]

What this PR does / Why we need it:

Pre-Submission Checklist:

• Did you explain what problem does this PR solve? Or what new features have been added?
• Have you added related test cases?
• Have you modified the related document?
• Is this PR backward compatible?

[zhaohuabing]

@tanjunchen why we need this?

[tanjunchen]

/retest

[tanjunchen]

@tanjunchen why we need this?

@zhaohuabing

1. Fix the bug that .Release.Namespace does not exist，refer to https://github.com/aeraki-mesh/aeraki/pull/336/files#diff-43173311cbcbb96cd0467f3399e82b42a7ac4bfbda0a5697de6e5260c33389e0L22
2. According to https://github.com/istio/istio/blob/master/manifests/charts/base/templates/clusterrolebinding.yaml#L9 We can add namespace for Charts yaml files

[zhaohuabing]

Do we have to change the name?

[tanjunchen]

It is not necessary, for installing multiple aeraki on the same cluster, this should be modified

[zhaohuabing]

It's ok to use the same name for multiple Aeraki deployments since they're in different namespaces.

[tanjunchen]

Installing aeraki in different namespace, aeraki failed to start.
Refer to the istio document, it is recommended to use different clusterrole and clusterrolebinding.

[zhaohuabing]

Hold this until we have a clear design how multi-tenants would work.

[zhaohuabing]

This PR is related to #330

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tanjunchen]

/reopen