[Feature] Dynamic route support

### Search before asking

- [x] I had searched in the [issues](https://github.com/labring/laf/issues?q=is%3Aissue) and found no similar issues.

### Feature Request

I hope to support dynamic route resolution. Currently, routes can only be accessed through file names, and the API designed in this way is difficult to comply with the design principles of RESTful API. You can put the settings in the yaml file, such as adding a `path` parameter.

```JavaScript
// not support
/users/{id}
```

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Start by locating the route-resolution entry point and the YAML configuration handling described in the issue. Check how file names currently become accessible routes, then define how a configured path such as /users/{id} should resolve and how completion will be verified. The issue does not mention specific files or tests.

Written by the indexing model from the issue text.