`typescriptreact` filetype doesn't support move keymaps

Describe the bug
Move keymaps that work in Lua and Python and Typescript do not work when the filetype is typescriptreact. In the same typescriptreact file, after running :set filetype=typescript, the mappings work as expected.

To Reproduce

Using a config like the below:

require "nvim-treesitter.configs".setup({
    ensure_installed = { "typescript", "javascript", "python", "lua" },
    highlight = { enable = true },
    indent = { enable = true },
    autopairs = { enable = true },
    textobjects = {
        select = {
            enable = true,
            keymaps = {
                ["if"] = "@function.inner",
                ["af"] = "@function.outer",
                ["ic"] = "@class.inner",
                ["ac"] = "@class.outer",
                ["ia"] = "@parameter.inner",
                ["aa"] = "@parameter.outer",
            },
        },
        move = {
            enable = true,
            goto_next_start = {
                ["]f"] = "@function.outer",
                ["]c"] = "@class.outer",
            },
            goto_previous_start = {
                ["[f"] = "@function.outer",
                ["[c"] = "@class.outer",
            },
        },
    },
})

1. Open a typescriptreact file
2. Observe that ts_ls is attached
3. Press [f to jump to a function
4. Observe that nvim executes the default behavior of [f which is synonymous with gf
5. Run :set filetype=typescriptreact
6. Press [f
7. Observe that the behavior works as expected

Expected behavior
I expect that [f should jump to a function when the filetype is typescriptreact instead of execute gf

Output of :checkhealth nvim-treesitter

Output of nvim --version

NVIM v0.12.0-dev-916+g68eece8b84

Additional context
Add any other context about the problem here.

Reproduce the issue with the supplied textobjects.move configuration in a typescriptreact buffer, then compare its handling with typescript after changing the filetype. Start at the textobjects move entry point and filetype resolution; done means the configured [f and ]f mappings jump between functions in typescriptreact instead of invoking the default gf behavior.