jigold

@williambrandler Could you please respond to Dan's questions? Thank you!

I'm not sure how I feel about the warning / error suggestion when always run jobs have inputs that aren't always copied out. Cleanup jobs shouldn't care whether the outputs...

Hopefully the new warning gets at the case you were thinking of as well as a more general problem beyond `always_copy_output`

Let's leave the WIP tag on, but this should be all set.

We cannot take off WIP and merge this until November 1st.

I'm going to rip out the currency code part because the ip fee and service fee are all in USD.

This failed because of a Query bug. It's ready for another look. Once you're happy with the structure of the code, I'll do one last dev deploy and check everything...

@danking I just want to double check you are okay with this change before it goes on. I'm going to do one more pass on dev deploy to make sure...

The resource names are changing to include the regions. So yes, this PR will use the latest resources. The backwards compatibility is for right when the front end starts up...

I added an optimization so we prefer the default location if we haven't had many failures creating instances. This will resolve my concerns about unnecessarily charging users more with this...