Current behavior (how does the issue manifest):
The lambda invoke activity returns a value object which includes the payload and the []byte serialized response. This really has no real purpose and causes confusion between the unmarshaled payload in the return param result .

Expected behavior:
Remove the value param, as both the unmarshaled payload and the status are both returne

Feature request

While the PR supabase/gotrue-js#195 adds listUsers, perhaps it should be renamed findUsers since the GoTrue implementation supports a find filter using FindUsersInAudience that finds users with the matching audience with a filter option and a sort:

if filter != "" {
	lf := "%" + filter + "%"
	// we must specify the collation in order to get case