Update blenderproc to accommodate blender's introduction as a python module

Hi,

I noticed that blender in version 3.4 has updated to be provided as a python module ([bpy](https://pypi.org/project/bpy/
))

This means that we can use our own python environment instead of the blender python environment, and use blender as python module as all modules in python.

This is a huge improvement since we can now use **our own** python modules and python environment ( without using addons) and debug in our specific development environment. ( without using pycharm professional for example)

I used the blenderproc package and tweaked it a bit so I can use my own python environment with the bpy package to render images, instead of running blender as an executable as it is now, and it worked great.

Do you plan to upgrade blenderproc for this change? A lot of your pipeline is around that constraint of blender's python environment, so you can safely remove some setup stages.

Start by reviewing BlenderProc's current setup stages and the path that runs Blender as an executable, then compare them with the bpy package approach described in the issue. Done means BlenderProc can use an external Python environment with bpy and the setup stages constrained by Blender's bundled Python environment are updated accordingly.

Written by the indexing model from the issue text.