A resource can be acquired even from the closed pool

keypool version: 0.4.7

Even when the state of the pool is PoolClosed a new resource can still be acquired.
Should an exception be thrown at this case?

Example:

val pool = KeyPool
  .Builder(
    (i: Int) => IO.ref(i),
    (r: Ref[IO, Int]) => IO.unit
  )
  .build
  
for {
  closedPool <- pool.use(kp => IO.pure(kp)) 
  _          <- closedPool.take(1).use { ref => 
    ref.get.flatMap(value => IO.println(s"created a new ref in the closed pool: $value"))
  }
} yield ()

Output:

created a new ref in the closed pool: 1

Start by reproducing the issue with the Scala example in the report, then trace how PoolClosed is handled during take. Confirm the intended closed-pool behavior with the existing pool lifecycle code and tests; done means a closed pool cannot acquire a new resource and the behavior is covered by a regression test.