Make scenario steps for roles match regex

[andrewstucki]

Found out that we had an acceptance test that was being skipped due to a non-matching regex in the scenarios, this adjusts the scenario so we don't see this anymore:

You can implement step definitions for undefined steps with these snippets:
func roleShouldHaveMembersAndInCluster(arg1, arg2, arg3, arg4 string) error {
	return godog.ErrPending
}
func userShouldBeAbleToReadFromTopicInCluster(arg1, arg2, arg3 string) error {
	return godog.ErrPending
}
func InitializeScenario(ctx *godog.ScenarioContext) {
	ctx.Step(`^role "([^"]*)" should have members "([^"]*)" and "([^"]*)" in cluster "([^"]*)"$`, roleShouldHaveMembersAndInCluster)
	ctx.Step(`^user "([^"]*)" should be able to read from topic "([^"]*)" in cluster "([^"]*)"$`, userShouldBeAbleToReadFromTopicInCluster)
}

[andrewstucki]

This change is a bit funny, but it matches how the scenario's step definition is actually written, the regex contains a single capture group for the members string and then has this logic:

	if strings.Contains(members, " and ") {

which basically means that it's tokenizing a single quoted string around an optional and inclusion in the string itself. This should probably eventually be rewritten to not be so weird and at some point I might take a look to see if godog's step parsing logic allows you to do thing like have a +-based capture group where you can treat it like an array or something, but for now this is just to minimally get this matching what it's supposed to do.

[chrisseto]

Looks like this will need to be rebased @andrewstucki. You're hitting the rackwareness flake.