refactor(coral): Improve ACL request form

# What is the problem?

Because there are multiple dependencies between the possible fields and field states, he ACL request form is very complex, both for the user and for developers working on it.

Some more UI research is necessary to solve common issues encountered when using the form. This and following comments is an example of the kind of explanations necessary for its use and understanding: https://github.com/aiven/klaw/pull/1119#issuecomment-1538483310

# How could this be improved?

- Reflect on possibly merging fields which have strong tw-ways dependencies, like `Topic name` and `Environment`: instead of each field dynamically rendering different options depending on the value of the other, render one field allowing to pick a topic from an environment in one action.

- Reflect on the appearing/disappearing fields depending on the options chosen (disabling the "Prefix" option and auto selecting "Literal" if the environment is an Aiven cluster, for example)

- Reflect on the organization and hierarchy of fields to reflect the mental model of a user wanting to create a new ACL (possibly having the Producer /Consumer distinction being made earlier in the UI with two buttons / a dropdown button in the Topic overview "Subscribe as a consumer" "Subscribe as a producer")

# New form design

After further research, this is the new ACL form design:

# Is this a feature you would work on yourself?

* [ ] I plan to open a pull request for this feature