feat: support multiple backend configurations

[ziwiwiz]

feat: support multiple backend configurations

[hsuyelin]

Thanks for your PR! This contribution is really meaningful. When I wrote the code earlier, I only considered my current needs and didn’t account for multiple backends. I’ve reviewed your code, and it looks good overall. Just wanted to check—have you tested it locally? Here are some test cases I’ve been thinking about:

1. Single backend: Configure the backend path and address correctly and check if it redirects properly. Expected result: It should successfully redirect to the specified backend and play.

2. Single backend: Configure an incorrect backend path and address that do not match the backend settings in the config file. Expected result: It should fail to match and print an error.

3. Multiple backends: Configure the backend path and address correctly and check if it redirects properly. Expected result: It should successfully redirect to the specified backend and play.

4. Multiple backends: Mix correct and incorrect backend paths and addresses. Check if the correctly configured backends can play properly (expected: they should play). Check if the incorrectly configured backends can play properly (expected: they should not play, and a log should be printed).

If you’ve already tested these cases, I’ll go ahead and merge the code into the main branch. This is really exciting—I’m looking forward to your reply!