feature: make path-pattern mapping dynamic and scalable

[dheerapat]

Currently your back-end API have only one, static path for external_wisdom pattern which is too rigid and hard to scale. As mentioned in #44

I added a new way to dynamically map each path to each pattern and easy to scale further.

This is not a breaking change, It still compatible with the original code, you will be able to run the same HTTP call without error. But now you will have more flexibility on the back-end side.

[danielmiessler]

This has conflicts, unfortunately, and I'm not sure I'm fully grasping the idea. Can you restate?

[dheerapat]

This has conflicts, unfortunately, and I'm not sure I'm fully grasping the idea. Can you restate?

example: currently when I go to localhost:5000/extwis I can send a post request to tell the server to mill my input with your pattern and then send to OpanAI to get the answer

I proposed that instead you building @app.route("/extwis", methods=["POST"]) for every pattern, we can just make path /<pattern> dynamic by adding a mapping dictionary to map path with the pattern user want to use. more info on this