Refactoring Citadel about zitadel HOT 10 CLOSED

• Maybe it makes sence to create an eventstore clienthelper before we start refactoring, because eventstore client produces a lot of repeated code

from zitadel.

• Config handling got too complex (management especially)

from zitadel.

• Tests:

`
func Test_ExistisPerm(t *testing.T) {

type args struct {
	existing []string
	perm     string
}
tests := []struct {
	name   string
	args   args
	result bool
}{
	{
		name: "not existing perm",
		args: args{
			existing: []string{"perm1", "perm2", "perm3"},
			perm:     "perm4",
		},
		result: false,
	},
	{
		name: "existing perm",
		args: args{
			existing: []string{"perm1", "perm2", "perm3"},
			perm:     "perm2",
		},
		result: true,
	},
}
for _, tt := range tests {
	t.Run(tt.name, func(t *testing.T) {
		result := ExistsPerm(tt.args.existing, tt.args.perm)
		if result != tt.result {
			t.Errorf("got wrong result, expecting: %v, actual: %v ", tt.result, result)
		}
	})
}

}
`

from zitadel.

• Logging and loglevels (@fgerschwiler i moved this to a seperate issue)

from zitadel.

Tracing (@fgerschwiler i moved this to a seperate issue)

• Add in auth to find out where we have performance problems
• implement more where needed

from zitadel.

What is public and what private, eg id in paramet of a function should be private (lower case)
Define how to write abbreviations like ID, IAM, URL

from zitadel.

• converting method naming concept

from zitadel.

• test files in other package --> (Gleiches Package)

from zitadel.

• I would rename the method Process of eventstore/pkg/query/Handler interface to Reduce

from zitadel.

• define where to set search limit ( app)

from zitadel.