feature: fix decoupled router uuid bug

The package drupal/decoupled_router has made an update to 2.0.6 in which they have removed a check on whether an entity uses a uuid instead of an id, see git blame here

This is due to this issue here in which the rationalization was laid out in comment #12:

I found the solution that patch #2 presents to be the best approach…because when the logic determined that the entity could use UUID instead of ID, the regex fails because UUIDs have are not only numbers. So, removing the whole idea of "param uses uuid" makes the most sense to me. I don't see the benefit of using UUIDs in this situation anyway.