[ISSUE #679] Fix judgment of topic route equality and optimize loadBalancer

[redlsz]

Which Issue(s) This PR Fixes

Fixes #679

Brief Description

1. correct judgment of topic route equality
2. do not reset index when update loadBalancer

[leizhiyuan]

add some ref

protocmp

it seems only proto.Equal can be used in production code

where protocmp can be used in test (for best practice)

Why does reflect.DeepEqual behave unexpectedly with protobuf messages?
Generated protocol buffer message types include internal state which can vary even between equivalent messages.

In addition, the reflect.DeepEqual function is not aware of the semantics of protocol buffer messages, and can report differences where none exist. For example, a map field containing a nil map and one containing a zero-length, non-nil map are semantically equivalent, but will be reported as unequal by reflect.DeepEqual.

Use the proto.Equal function to compare message values.

In tests, you can also use the "github.com/google/go-cmp/cmp" package with the protocmp.Transform() option. The cmp package can compare arbitrary data structures, and cmp.Diff produces human-readable reports of the differences between values.

if diff := cmp.Diff(a, b, protocmp.Transform()); diff != "" {
t.Errorf("unexpected difference:\n%v", diff)
}

[lizhanhui]

A few follow-up issues to resolve:
1, Test cases are required to verify this change, which also ensures future changes will not break;
2, CI is broken

[redlsz]

A few follow-up issues to resolve: 1, Test cases are required to verify this change, which also ensures future changes will not break; 2, CI is broken

1. done
2. It seems to be not related to this issue.

[lizhanhui]

Nice work