20w18a - Fishing Broken with new version

Attempting to fish results in the bubbles spawning and the splash/bobber effect occuring as normal, but attempting to right-click to reel in the fish results in nothing happening. No fishing result, no exp gained, no durability lost from the rod. There is a delay between being able to reel it in after this occurs.

To replicate, simply try to fish using a rod in the latest snapshot.

Attached is the latest error log from the server, showing several fishing attempts.

Here is the error from the server window:

```[14:43:02] [Server thread/FATAL]: Error executing task on Server
java.lang.NullPointerException: null
at be.b(SourceFile:183) ~[server.jar:?]
at bi.a(SourceFile:32) ~[server.jar:?]
at bdo.b(SourceFile:478) ~[server.jar:?]
at biv.a(SourceFile:23) ~[server.jar:?]
at bjh.a(SourceFile:212) ~[server.jar:?]
at yv.a(SourceFile:273) ~[server.jar:?]
at zl.a(SourceFile:1000) ~[server.jar:?]
at sp.a(SourceFile:31) ~[server.jar:?]
at sp.a(SourceFile:9) ~[server.jar:?]
at nh.a(SourceFile:21) ~[server.jar:?]
at uo.run(SourceFile:18) ~[server.jar:?]
at alu.c(SourceFile:144) [server.jar:?]
at aly.c(SourceFile:23) [server.jar:?]
at net.minecraft.server.MinecraftServer.b(SourceFile:789) [server.jar:?]
at net.minecraft.server.MinecraftServer.c(SourceFile:159) [server.jar:?]
at alu.w(SourceFile:118) [server.jar:?]
at net.minecraft.server.MinecraftServer.bc(SourceFile:771) [server.jar:?]
at net.minecraft.server.MinecraftServer.w(SourceFile:765) [server.jar:?]
at alu.c(SourceFile:127) [server.jar:?]
at net.minecraft.server.MinecraftServer.v(SourceFile:750) [server.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:702) [server.jar:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_221]```

I have tested using an unenchanted rod and a different mixture of enchantments to be sure it isn't the result of a single enchantment:

1) Unenchanted: same bug and error

2) Mending: same bug and error

3) Lure 3: same bug and error

4) Luck of the Sea 3: same bug and error

5) Unbreaking 3: same bug and error

I have also tested this offline on a newly created world, with the same bug and error generated.