Linking: Params are not parsed correctly when a screen appears in multiple configs

Current behavior

I have this config:

const config = {
  screens: {
    Tabs: {
      screens: {
        Sortiment: {
          path: "sortiment",
          screens: {
            Category: {
              path: "k/:category?",
              exact: true
            }
          }
        },
        Home: {
          path: "home",
          screens: {
            Category: "category"
          }
        }
      }
    }
  }
};

And I'm trying to parse this path:

const path = "k/categoryParam?x=x";

The state object that is returned when I call getStateFromPath(path, state) looks like this:

{
    "routes": [
        {
            "name": "Tabs",
            "state": {
                "routes": [
                    {
                        "name": "Sortiment",
                        "state": {
                            "routes": [
                                {
                                    "name": "Category",
                                    "path": "k/categoryParam?x=x",
                                    "params": {
                                        "x": "x"
                                    }
                                }
                            ]
                        }
                    }
                ]
            }
        }
    ]
}

Notice how categoryParam is not included in the routes params. If you remove the second path config inside the "Home" config, the params are parsed correctly.

I tracked the problem down to this line:
https://github.com/react-navigation/react-navigation/blob/838842e85fffd56a3a64a1f4e969318998217c7a/packages/core/src/getStateFromPath.tsx#L287

In this case there are two configs that can be found here, and the wrong one is used to construct the params.

Expected behavior

params should include the category param and look like this:

{
     "category": "categoryParam",
     "x": "x"
}

Reproduction

https://codesandbox.io/s/npm-playground-forked-pnv716?file=/src/index.js

Platform

• Android
• iOS
• Web
• Windows
• MacOS

Packages

• @react-navigation/​bottom-tabs
• @react-navigation/​drawer
• @react-navigation/​material-bottom-tabs
• @react-navigation/​material-top-tabs
• @react-navigation/​stack
• @react-navigation/​native-stack

Environment

• I've removed the packages that I don't use

Start in packages/core/src/getStateFromPath.tsx at the line linked in the issue, where multiple matching configs are found and one is used to construct params. Use the provided config and path as the reproduction, then verify that the resulting Category route includes both category and x params.