Fix oom_error function argument

[jipolanco]

First of all, thanks for this really useful package!

I detected an issue in the latest (v0.3.0) version of Bumper.jl. The oom_error function is called with a single argument b::AllocBuffer in:

Bumper.jl/src/Bumper.jl

Lines 68 to 73 in 55d0ded

	function alloc_ptr(b::AllocBuffer, sz::Int)
	ptr = pointer(b) + b.offset
	b.offset += sz
	b.offset > sizeof(b.buf) && oom_error(b)
	ptr
	end

However, the only definition of oom_error takes no arguments:

Bumper.jl/src/Bumper.jl

Lines 82 to 85 in 55d0ded

	@noinline function oom_error()
	error("alloc: Buffer out of memory. This might be a sign of a memory leak.
	Use Bumper.reset_buffer!() or Bumper.reset_buffer!(b::AllocBuffer) to reclaim its memory.")
	end

Even in cases where the OOM error is never reached, this causes JET.jl to complain when analysing code which uses Bumper.jl.

This PR fixes the issue by including an unused positional argument to oom_error.

[MasonProtter]

Oh good catch, thank you!

I think I meant to make oom_error report how many bytes were allocated, but it's not really the most useful information so I think for now I'll leave it like this with the unused argument for now.