Fix webapp configs

[jimallman]

Cleanup and consolidation of Ansible configuration of our web-apps

• simplify API base URLs and endpoints
• add explicit production API base URLs (used in dev deployment for some API calls)
• rename some confusing Ansible variables (and filenames) and web-app config keys
• check current playbook's roles (via role_names) to adjust apache config for API vs. web-app vs. others TBD

NB - This is working on devtree, along with a companionfix-webapp-configs PR in opentree.

[jimallman]

This could probably use a final review for our always-on-production endpoints. If necessary, we can use both dev (default) and production versions of a method, by defining two different endpoints in our config, like so (and using both names as appropriate in the web-app code):

# a typical endpoint, on both default/dev and production
getContextForNames_url = {default_apis}/v3/tnrs/infer_context
PRODUCTION_getContextForNames_url = {production_apis}/v3/tnrs/infer_context

# and this is a cached call for both default/dev and production
getSynthesisSourceList_url = {CACHED_default_apis}/v3/tree_of_life/about
PRODUCTION_getSynthesisSourceList_url = {CACHED_production_apis}/v3/tree_of_life/about

[snacktavish]

This branch was merged into development - can we delete this branch "fix-webapp-configs" and work from development?

[snacktavish]

I merged most of these into development, and used that to deploy production phylesystem-api! Can we move the webhook deploy commit to a new branch off of development?

[jimallman]

Can we move the webhook deploy commit to a new branch off of development?

Agreed. Moving these changes to a new branch, and closing this one.