python class decorators are mistaken as startpoint for undecorated classes defined after it

Describe the bug
When multiple classes are defined in a single python file, and one or more classes are decorated with dataclasses.dataclass, this plugin mistakes that line as the start point for non-dataclasses defined after it and before any other dataclass.

To Reproduce
Steps to reproduce the behavior:

1. Copy the following example code into a new python file:

import dataclasses


@dataclasses.dataclass
class SomeDataClass:
    name: str


class SomeClass:
    def __init__(self):
        pass


class SomeOtherClass:
    def __init__(self):
        pass

2a. Place cursor somewhere inside SomeClass
2b. Callrequire("nvim-treesitter-textobjects.select").select_textobject("@class.inner", "textobjects") directly or via keybind
2c. Observe that the contents of SomeDataClass are selected instead of SomeClass

3a. Place cursor somewhere inside SomeClass
3b. Callrequire("nvim-treesitter-textobjects.select").select_textobject("@class.outer", "textobjects") directly or via keybind
3c. Observe that both SomeClass and SomeDataClass are selected instead of just SomeClass

4a. Place cursor somewhere inside SomeOtherClass
4b. Callrequire("nvim-treesitter-textobjects.select").select_textobject("@class.inner", "textobjects") directly or via keybind
4c. Observe that the contents of SomeDataClass are selected instead of SomeOtherClass

5a. Place cursor somewhere inside SomeOtherClass
5b. Callrequire("nvim-treesitter-textobjects.select").select_textobject("@class.outer", "textobjects") directly or via keybind
5c. Observe that all three classes are selected instead of just SomeOtherClass

Expected behavior
When selecting @class.inner or @class.outer, the class the cursor is inside of should be selected, not the previous dataclass and not multiple classes.

Output of :checkhealth nvim-treesitter

Output of nvim --version

NVIM v0.11.3
Build type: RelWithDebInfo
LuaJIT 2.1.1748459687
Run "nvim -V1 -v" for more info

Additional context
Add any other context about the problem here.

Start at require("nvim-treesitter-textobjects.select").select_textobject("@class.inner", "textobjects") and the corresponding @class.outer path, then reproduce the example with the Python parser. Trace how the class selections are determined and verify that each class selects only its own inner or outer range, rather than including the preceding dataclass.