Remove secureroute component and react-router dependency

[pavinduLakshan]

Purpose

SecureRouter component in React SDK allows defining protected routes in a React app, when the used routing library is the React Router[1], but it isn't without its own complexities and tech debt introduced to the SDK.

1. Securing routes is out of scope of an authentication SDK. It's up to the application to secure its routes, using the functions provided by the SDK (such as isAuthenticated)
2. Introducing SecureRoute has resulted in a tightly coupled integration with the React Router library.
3. SecureRoute is based on the custom routes feature in React Router v5, which is no longer available in v6 and onwards. [2] Therefore, applications using a React router version higher than v6 are unable to use the SecureRoute component.

Due to the above reasons, we are planning to remove SecureRoute component from the React SDK. Instead, we are adding example code snippets to the API documentation for securing app routes using several prominent routing libraries.

Related Issues

• Fixes Bring your own router: Remove react-router-dom dependency #230
• Fixes React Router version defined is too harsh #137

[1] https://reactrouter.com/en/main
[2] https://gist.github.com/mjackson/d54b40a094277b7afdd6b81f51a0393f

[pavinduLakshan]

Marked as draft until the documentation work and internal discussions are concluded.