feat: allows to define rules that are enabled when a given value is a partial match to a target attribute

[3846masa]

Fix #1188

This PR is a feature request.

In Bucketeer rules, there are contains (= Clause.Operator.IN), which is essentially the same behavior as Clause.Operator.PARTIALLY_MATCH.

This PR defines an Operator that can specify a condition on whether a user's attribute partially matches a given value.

---

This pull request introduces a new clause operator, PARTIALLY_EQUALS, and integrates it across the codebase. The changes span multiple files, including Go source files, protocol buffer definitions, and UI components.

New Clause Operator Implementation:

• evaluation/clause_evaluator.go: Added a new case featureproto.Clause_PARTIALLY_EQUALS in the Evaluate method and implemented the partiallyEquals function to check if the target value contains any of the specified values. [1] [2]

Protocol Buffer Updates:

• proto/feature/clause.pb.go: Introduced Clause_PARTIALLY_EQUALS with value 12 and updated the corresponding maps and descriptors to include this new operator. [1] [2] [3] [4] [5] [6]
• proto/feature/clause.proto: Added PARTIALLY_EQUALS to the Clause enum.

UI Integration:

• ui/web-v2/src/assets/lang/en.json: Added the English translation for the partiallyEqual operator.
• ui/web-v2/src/assets/lang/ja.json: Added the Japanese translation for the partiallyEqual operator.
• ui/web-v2/src/components/FeatureTargetingForm/index.tsx: Included the PARTIALLY_EQUALS operator in the clause comparison operator options.
• ui/web-v2/src/lang/messages.ts: Defined the message for the partiallyEqual operator.
• ui/web-v2/src/proto/feature/clause_pb.js: Updated the Clause.Operator object to include PARTIALLY_EQUALS.

[cre8ivejp]

Thank you so much for your contribution!

The PARTIALLY_MATCH is a better fit for this case.
Could you update the other places?

Suggested change

	PARTIALLY_EQUALS = 12;
	PARTIALLY_MATCH = 12;

[3846masa]

@cre8ivejp
I recreated the commit to have PARTIALLY_MATCH.

[cre8ivejp]

@3846masa, to fix the CI issues, you must update the generated proto files using the command make proto-all at the project's root and push the changes.
Are you working in the GitHub Dev Container? If so, you just need to run the command above because the container already contains all the necessary tools. Otherwise, you will need to install the tools on your local machine.

[3846masa]

@cre8ivejp
I executed make proto-all in VSCode Dev Container.

[kentakozuka]

Thanks! Amazing improvement 🎉

[cre8ivejp]

@3846masa, please rebase your branch to fix the conflict, so we can merge it.

[3846masa]

@cre8ivejp I was rebased and fixed conflict.

[cre8ivejp]

Thank you!