Fix ai binding logs property

[G4brym]

This re-adds a removed property as backwards compatibility, removed in the last release

[DaniFoldi]

Hi, I saw the workers-sdk test broken by the removal of this property. Just curious, if you can share, is there any particular reason the logs were removed/hidden in the first place?

Something like AI is much more complicated than say KV - there's not much to log in the case of KV (put or delete, that's it), but with AI, many things can happen, and logs were useful for me (and probably other folks who found them).

[G4brym]

Hey @DaniFoldi logs are not structured, and we change their format all the time
Since the beginning it was meant to be used just internally by the team to debug some models, and we have now moved on to a better logging solution
We are just not in a position currently to guarantee that the logs will keep the same structure going forward, and because we cannot guarantee their format it's better to not expose them as users, like you, might start relying on them
Maybe in the future, when and if we add custom models we might bring back logs in an official format

[RamIdeas]

FYI we've decided to hold off upgrading workerd in wrangler until this PR lands and is released cloudflare/workers-sdk#5752 (comment)