CLN: enforce the deprecation of exposing blocks in core.internals

[natmokval]

xref #55355,
enforced the deprecation of create_block_manager_from_blocks

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

[mroeschke]

Suggested change

	ifVersion(pyarrow.__version__) =="10.0.1":
	pytest.skip("skip the pyarrow version '10.0.1'")
	pytest.importorskip("pyarrow", "10.0.1")

And similar below

[natmokval]

thanks for your help. It seems that it doesn't work when using pytest.importorskip("pyarrow", "10.0.1"), but it works properly with pytest.importorskip("pyarrow", "11.0.0")

[mroeschke]

Thanks @natmokval

[jorisvandenbossche]

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

[jorisvandenbossche]

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 #50578 (comment)

[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

thanks @jorisvandenbossche, I opened PR to revert this