fix: update dependency babel-plugin-styled-components to v1.13.3 (release-bot/next-v15.x)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
babel-plugin-styled-components (source)	1.12.1 → 1.13.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

styled-components/babel-plugin-styled-components (babel-plugin-styled-components)

v1.13.3

Compare Source

• when there are multiple assignments prefer the outer name (#​355) thanks @​rockwotj
• minor dependency updates

v1.13.2

Compare Source

• added some conditional guards to code paths that lead to errors for some consumers (0c16c1b)
• dependency updates
• teach babel plugin about certain spread application scenarios with "css" prop #​339
• handle namespace import (import * as styled from 'styled-components') properly #​340

v1.13.1

Compare Source

Fix one edge case with object key interpolation from v1.13.0

v1.13.0

Compare Source

• teach the plugin how to handle variable interpolation in object keys, e.g.

  css={{
    [theme.breakpoint.sm]: {
      color: 'red'
    } 
  }}

• plugin now emits transient props when replacing css prop calls (cuts down on garbage in the DOM for s-c 5.1+)

• merge withConfig arguments to allow for shouldForwardProp, thanks @​ithinkdancan #​323

• move injected components to end of file scope, thanks @​sfishel18

• Ensure sc- prefix is always added #​313, thanks @​chalbert

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[ZauberNerd]

The babel plugin has a bug in conjunction with TypeScript which we need to debug and probably fix upstream, since the bug has been there for quite a while: #2118 (comment)