Allow unconnected users to browse Dapp

[leirbag95]

Linked to this issue #21

Description: This pull request aims to enhance the user experience by removing the requirement for users to be connected in order to browse the Dapp and create instances. It introduces changes to the application flow to facilitate access for unconnected users while maintaining the necessary functionalities related to instance creation.

Changes:

• Allow Unconnected Browsing: Users can now access and browse the Dapp without requiring a prior connection.
• Streamlined Instance Creation Process: Modified the instance creation process to function seamlessly for unconnected users.
• User Experience Enhancement: Ensured a smoother flow for unconnected users while preserving the necessary authentication steps during critical operations. Benefits:

Improved accessibility for users, allowing them to explore the Dapp and initiate the instance creation process without the barrier of mandatory prior connection. Enhanced user experience by streamlining the onboarding process.

Screenshots:

Code: I removed the redirection from useConnectedWard.ts file

export default function useConnectedWard(route = '/') {
  const [state] = useAppState()
  const router = useRouter()

  useEffect(() => {
    if (!state.account) {
      router.replace(route)
    }
  })
}

And add same button as Header at the end of instance creation process

[claudioALEPH]

You only added the button on the new function page. Each product pages need to have this behavior, since they all require at least a message to be sent.

Recreating the "wallet picker" at the bottom of the page does not make much sense to me. The button below the "Holding Requirements" section should scroll to the top of the page.

Besides, when trying to connect using that button, an error is issued because the default behavior of a button is to send the parent form it is contained in.

Totally agree!

[amalcaraz]

Closing this PR. This should be refined more in detail.