fix: send in/out to transition fn

[tivac]

After #3918 was fixed by #8068 it was noticed by @robertadamsonsmith that if your transition function is used as a combined in/out transition, it still receives { direction: 'both' } when running the function instead of in or out depending on the direction the transition is going. This severely limits the utility of passing the direction value in the first place.

#3918 (comment)

I agree with him that this is a bug in the original version of #8068, so I'm sending this PR in the hopes that we can get that corrected before too long.

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with npm test and lint the project with npm run lint

[vercel]

@tivac is attempting to deploy a commit to the Svelte Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
svelte-dev-2	❌ Failed (Inspect)			Feb 24, 2023 at 3:39PM (UTC)

[tivac]

I dunno what to do with this vercel deployment failure, I tried the "inspect" link but I wasn't able to get access to anything to debug it. Can someone maybe re-kick it for me just in case it's a transient issue?

[tivac]

I could also update this to add a second parameter like options.current or options.currentDirection so that direction can remain as-is, if it'd help this get merged since it would no longer be a breaking change. 👍🏻