Make tutorial setup more like a common dev setup

[droumis]

The tutorial relies on anaconda-project, which no one uses for actual development/analysis with HoloViz and therefore I don't think it's helping new users understand how to utilize HoloViz. Instead, I think the tutorial setup should include a path which doesn't rely on anaconda-project and is more like:

1. install miniconda
2. create/activate dev env from env.yml
3. download required data for tutorial

[maximlt]

While I also wish we could move away from anaconda-project, I don't know if we can provide a reliable setup that is easier than this:

conda create -n project "anaconda-project>=0.11"
conda activate project
anaconda-project download pyviz/holoviz_tutorial
cd holoviz_tutorial # You may need to delete this directory if you've run the command above before
anaconda-project run jupyter notebook

[droumis]

I'm not so much referring to ease in terms of number of commands being run, but rather how the approach translates into an actual workflow that users will employ while doing their own work with HoloViz, which is not using anaconda-project.