Python 3 Migration: Cutter Bug fix

[tst-cjeffries]

Fixes import and unicode issues stemming from the python 3 migration. Do not merge until the Python 3 Server migration PR is merged.

To test:

1. Build and install according to the build docs (https://github.com/tst-cjeffries/earthenterprise/blob/python_3_cutter_bug/earth_enterprise/BUILD_RHEL_CentOS.md)
2. Run the tutorials. sudo /opt/google/share/tutorials/fusion/download_tutorial.sh sudo cp earthenterprise/earth_enterprise/src/fusion/tools/gee_test/tutorial_files/providers.xml /gevol/assets/.userdata/ sudo env "PATH=$PATH:/opt/google/bin" earthenterprise/earth_enterprise/src/fusion/tools/gee_test/run_tutorial.sh Then wait until the tutorials are finished building. This can be monitored in with the status scripts in that same directory. sudo env "PATH=$PATH:/opt/google/bin" earthenterprise/earth_enterprise/src/fusion/tools/gee_test/publish_tutorial.sh
3. sudo /opt/google/bin/gecutter enable
4. Launch cutter from the admin page and make both a 2d and 3d cut.
5. Verify the 2d and 3d cut by publishing them on the admin page and viewing them.
6. Run the glc assembly and disassembly on the 3d cut.
7. Verify the assembled glc by registering and viewing it.
8. Verify the disassembled glb by either moving it into /opt/google/gehttpd/htdocs/cutter/globes, registering it and viewing it or by loading it into portable.

[google-cla[bot]]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla[bot]]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[google-cla[bot]]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.