Issue943/pull deps neo4j

[Leahh02]

• beeflow core pull-deps should use a Dockerfile to build the needed neo4j container and add the apoc file
• This dockerfile should be placed in beeflow/data/dockerfiles and should be used by the ci integration tests so we only need to modify it in one place.
• Also, if a user uses "beeflow core pull-deps" to have their own dependent containers, they should be used in the bee.conf file. Consider automatically editting it and removing the ~/.beeflow/deps directory. Beeflow should not be running when this is done, so adding a check for that should probably be done.

[Leahh02]

I'm working on the last part right now. I can change the name of beeflow/data/dockerfiles/Dockerfile.apoc_neo4j if needed. I can also remove beeflow/data/dockerfiles/Dockerfile.neo4j-ppc64le if needed.

[pagrubel]

I'm working on the last part right now. I can change the name of beeflow/data/dockerfiles/Dockerfile.apoc_neo4j if needed. I can also remove beeflow/data/dockerfiles/Dockerfile.neo4j-ppc64le if needed.

Yes, I think Dockerfile.neo4j would suffice and yes please remove the other. We will need to probably add one for arm architecture in the future.