fix(core): fix type ExtractStateValue to describe real state value

[jirutka]

Consider the following schema:

type LightStateSchema = {
  states: {
    green: {},
    yellow: {},
    red: {
      states: {
        walk: {},
        wait: {},
        stop: {},
      },
    },
  },
}

The current implementation of the ExtractStateValue type generates the
following type:

{
  green?: {} | undefined
  yellow?: {} | undefined
  red?: "walk" | "wait" | "stop" | {
    walk?: {} | undefined
    wait?: {} | undefined
    stop?: {} | undefined
  } | undefined
}

This does not describe the StateValue of LightStateSchema as provided
in State.value.

The new implementation generates the following type:

"green" | "yellow" | "red" | {
  red?: "walk" | "wait" | "stop" | undefined
}

[changeset-bot]

🦋 Changeset is good to go

Latest commit: f51614d

We got this.

This PR includes changesets to release 7 packages

Name	Type
xstate	Minor
@xstate/analytics	Major
@xstate/graph	Major
@xstate/immer	Major
@xstate/react	Major
@xstate/test	Major
@xstate/vue	Major

Not sure what this means? Click here to learn what changesets are.

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

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit f51614d:

Sandbox	Source
XState Example Template	Configuration
XState React Template	Configuration

[AliKholmatov]

Hi! In latest versions ExtractStateValue was deleted. What can I use instead of ExtractStateValue? Please)

[Andarist]

Could you open a discussion that would describe your use case? For context, this type was removed in #2828 as we've assumed that it was a leftover from a previous implementation and that it wasn't used externally.

[AliKholmatov]

@Andarist sorry I can't answer right now, I will try to figure out it. I guess it was used to make deal with TS