Fix useLocation to receive 0 instead of null when state is set to 0

[jungwoo3490]

Fixes #11448

I fixed location's state property value like this.

let location: Location = {
  pathname: locationProp.pathname || "/",
  search: locationProp.search || "",
  hash: locationProp.hash || "",
  state: locationProp.state ? locationProp.state === 0 ? 0 : locationProp.state : null, // fixed
  key: locationProp.key || "default",
};

Now, useLocation receive 0 instead of null when state is set to 0.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2cbb43f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[remix-cla-bot]

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳

[timdorr]

Can you remove the unrelated import changes?

[jungwoo3490]

Can you remove the unrelated import changes?

Sure!! I removed all of them :) @timdorr