raise Exception on endpoint collision + handle empty init

[erik-dunteman]

What is this?

We raise an Exception when routes are repeated

• standardization for endpoint routs to be "/"+route
• handling for route=None

plus a sidequest

• handling the case where context returns a non-dict
• handling the case where init isn't ran

Why?

Both endpoint collision and misuse of init were leading to user confusion

How did you test it works without regressions?

Local tests with multiple endpoints

• mixed (/route, route) cases to test the standardization
• mixed handler/background cases to test if collisions are still detected
• route=None case
• no init case
• init returning non-dict case

If this is a new feature what may a critical error look like?

not new feature, but technically a breaking change since we raise exceptions in these cases rather than silently fail.