Allow to create multiple components at once

### Describe the problem

For each localization component in a git project

1. I need to fill out the "add new component" form.
2. That scans my repo and suggests the potential candidates.
3. For this I first have to enter stuff which later gets partially ignored, since I selected the discovered component.
4. Then I need to fill out the rest of the form which contains defaults I don't want.
5. Then I need to store it.
6. Then I need to enter the component settings again, to edit settings which weren't shown to me before.
7. Then I need to go to the project root.
8. Then I hit the "components" tab.
9. Finally I can start with the next component.
10. I need to repeat all these steps *for every component* I want to add.

This is completely upside down to how it *actually* should be.
(And btw. you're seriously wasting user's time and annoy them with that procedure.)

### Solution brainstorm

What it *should* look like: Have a wizard which lets me add all or some components of a git project.

1. Enter Git URL.
2. Weblate scans, shows potential components.
3. I select all components I want.
4. I choose all settings which apply to all component types *once*.
5. I step through settings which only apply for a specific component.
6. I hit "Finish". Everything is setup up. All done.

### Side note: Defaults I constantly have to change:

- Manage strings, edit base file: Noooo, no translators should be able to mess with the source strings. The source *code* is the source of truth, not the other way around.
- Push on commit: No, I *don't* want pull requests every day.
- Merge style: Rebase is too error-prone.
- Lock on error: Errors all the time, would lead to too much lock time. (See my other issue #18241)
- Adding new translation: Random people should not be able to induce a PR which creates files in my project. Which then typically are empty. (And would be unused anyway, since I would also have to edit the project configuration to enable the new languege). I have to decline these PRs, but then Weblate is angry at me again.

### Describe alternatives you have considered

_No response_

### Screenshots

_No response_

### Additional context

I created this issue after I had a conversation with @orangesunny.