kingst-la2016: rephrase USB bulk transfer size padding constraint
Always round up capture data USB bulk transfer sizes to full EP 6 packet
sizes. The previous implementation suggested that it's only required for
smaller transfers, but it's just a coincidence that the upper limit of
256KiB happened to also be a multiple of the 512B packet size.
It's assumed that capping at the absolute size limit and always padding
is more readable and as reliable as the previous if-else logic was.
Rephrase the round up by means of integer multiplication instead of
bit twiddling. Compilers should get what is intended, humans may prefer
to read the former.