history trace for goBack: History: failed to execute a task:: timeout _reported_

### Description

goBack works as expected, but always log some errors in the console

### Reproduction Steps

Notes:

1- I use nextjs v9.5.2
2- FlippedArrow is an svg component

```

```

### Relevant Logs

```shell
error-reporting.js:205 failed to execute a task:: timeout
Vf @ v0.js:2
(anonymous) @ v0.js:4
g.error @ v0.js:1
(anonymous) @ v0.js:2
Promise.then (async)
Zi @ v0.js:2
Xi @ v0.js:2
g.goBack @ v0.js:2
g.Gg @ v0.js:2
wh @ v0.js:2
p @ v0.js:2
(anonymous) @ v0.js:2
vh @ v0.js:2
g.trigger @ v0.js:2
(anonymous) @ v0.js:2
error-reporting.js:205 history trace for goBack: History: failed to execute a task:: timeout _reported_
Vf @ v0.js:2
(anonymous) @ v0.js:4
g.error @ v0.js:1
(anonymous) @ v0.js:2
Promise.then (async)
Zi @ v0.js:2
Xi @ v0.js:2
g.goBack @ v0.js:2
g.Gg @ v0.js:2
wh @ v0.js:2
p @ v0.js:2
(anonymous) @ v0.js:2
vh @ v0.js:2
g.trigger @ v0.js:2
(anonymous) @ v0.js:2
v0.js:1 Uncaught (in promise) History: failed to execute a task:: timeout
at ta (https://cdn.ampproject.org/v0.js:1:3508)
at Db.g.createError (https://cdn.ampproject.org/v0.js:1:15358)
at https://cdn.ampproject.org/v0.js:2:165029
at https://cdn.ampproject.org/v0.js:2:164639
```
```

### Browser(s) Affected

Chrome, Firefox

### OS(s) Affected

_No response_

### Device(s) Affected

_No response_

### AMP Version Affected

2109272305001

Start with the provided AMP.goBack reproduction and the error-reporting.js and v0.js stack traces, then trace the goBack task path that reports the timeout. Reproduce it in Chrome or Firefox using the shown markup and determine whether the navigation succeeds while the console errors are emitted. Done means the successful goBack action no longer produces the reported timeout and history-trace errors.

Written by the indexing model from the issue text.