patch all the API repos to use project-name routes like we did last year

[MikeTheCanuck]

2018 disaster resilience API service is returning 404 Not Found error when requested via http://service.civicpdx.org/disaster-resilience or any sub-route.

We applied this fix last year to deal with co-hosting 5 apps on the same hostname (e.g. service.civicpdx.org/budget): https://github.com/hackoregon/team-budget/commit/8536aca0e1a8176dfe9e9063d55d319d80767ca9#diff-e927b8d55fea7a008487742f7e579663

It wouldn't surprise me that we need to make the same fix to the 2018 API projects as well.

• [x] disaster-resilience-backend
• [x] elections-2018-backend
• [x] housing-2018
• [x] neighborhoods-2018
• [x] transportation-systems-backend-2018

[MikeTheCanuck]

I'm testing this out right now on the DR project: https://github.com/hackoregon/disaster-resilience-backend/commit/12ff1266b8d2a8b31e1d4d9dfbb1d9f78539cbb4

After applying this fix and deploying, we now receive a 500 Internal Server Error. CloudWatch logs report: django.core.exceptions.ImproperlyConfigured: Specifying a namespace in include() without providing an app_name is not supported. Set the app_name attribute in the included module, or pass a 2-tuple containing the list of patterns and app_name instead.

[MikeTheCanuck]

I fixed that with this commit and now it's back to 404 errors: https://github.com/hackoregon/disaster-resilience-backend/commit/a453639cf2b9e6943a5330ba28731277a79077c7

[MikeTheCanuck]

Looks like the * and / fixes did the trick (at least until ECS and/or ALB started playing havoc with working setup).