CLN: enforce the deprecation of exposing blocks in core.internals 
xref #55355,
enforced the deprecation of `create_block_manager_from_blocks`

xref #55139
enforced the deprecation of exposing `blocks` in `core.internals `

Thanks @natmokval  I think we need to revert this, and first bump the DeprecationWarning to a FutureWarning. I actually don't care that much about the exact warning class, though, but I think that this is generally the correct way to deal with something we started deprecating with a DeprecationWarning. But I think we should care about keeping this around a bit longer (even though it is with a warning), because this simply means that you cannot use pandas 3.0 with pyarrow < 15, while we actually have a minimum version requirement of pyarrow 10 > I think that this is generally the correct way to deal with something we started deprecating with a DeprecationWarning

Which is similarly as Richard said in https://github.com/pandas-dev/pandas/issues/50578#issuecomment-2105676394 > I think we need to revert this, and first bump the DeprecationWarning to a FutureWarning. I actually don't care that much about the exact warning class, though, but I think that this is generally the correct way to deal with something we started deprecating with a DeprecationWarning. But I think we should care about keeping this around a bit longer (even though it is with a warning), because this simply means that you cannot use pandas 3.0 with pyarrow < 15, while we actually have a minimum version requirement of pyarrow 10

thanks @jorisvandenbossche, I opened [PR](https://github.com/pandas-dev/pandas/pull/58715) to revert this