[0.15.11] set_stack doesn't copy blueprint books' names

[theRustyKnife]

A call to LuaItemStack.set_stack with a LuaItemStack containing a blueprint book as an argument ignores the blueprint book's name and leaves it at the default. It also sets the selected blueprint to the first one instead of the one the original book had selected.
Interestingly, this doesn't seem to be an issue with blueprints on their own.

Cheers TRK

[Rseding91]

Thanks for the report. I've fixed it for the next version of 0.15.