This PR was merged into the 6.4 branch.

Discussion
----------

[DomCrawler][Form] Fix the exclusion of <template>

| Q             | A
| ------------- | ---
| Branch?       | 6.4 <!-- see below -->
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | Fix #53823
| License       | MIT

In the DomCrawler, the way to get fields via xPath avoid to find elements inside a `<template>` element:
```html
<form>
    <template>
        <input type="text" name="not_selected_because_in_template" />
    </template>

    <input type="text" name="selected_because_out_of_template" />
</form>
```

But, it appear it also exclude form elements if the `<form>` is in a `<template>` (eg: in a `<turbo-stream>`), that bug-fix keep the previous behavior but allow the following:
```html
<turbo-stream>
    <template>
        <form>
            <input type="text" name="selected_because_in_turbo_stream_1" />
            <input type="text" name="selected_because_in_turbo_stream_2" />
        </form>
    </template>
</turbo-stream>
```

As mentioned in #53823, an alternative should be to use `[not(ancestor::template/ancestor::form)]` in the xPath to allow:
```html
<template>
    <form>
        <input type="text" name="selected_because_parent_is_form_1" />
        <input type="text" name="selected_because_parent_is_form_2" />
    </form>
</template>
```

Commits
-------

db3a9dd [DomCrawler] [Form] Fix the exclusion of <template>