Enhancements for other chapters

[jakehobbs]

Chicago requested sending of event surveys, but they have not entered any events yet.

[jakehobbs]

Still no chapters outside of the Bay Area have entered attendance for any events, so features for them should not be working on currently. Send message to Ana R stating the same.

[jakehobbs]

More features for improving the experience for other chapters

Let other chapters update their own chapter's chapter data (social media links, organizers, etc.)

Run a goroutine to update the "last action" date based on events entered into attendance for other chapters. Then don't ask about their last action date on the monthly check-in email if they already had an action entered into the ADB?

Update model.UpdateActivistData to pass data to signup service for other chapters (for global list & other chapter's list). Update the signup service to handle it. (Make sure not to submit "interest forms" for non-Bay people.)

Allow "interest forms" to be submitted for people in other chapters when they sign a petition. (Enable Community Prospects page too, but call it "Leads.") The signup service should include a "chapter name" (or maybe even ID) when submitting to the interest form api. Then the form_processor queries should use that chapter_id instead of being hard-coded for SF Bay (47).

Look for instances of "SF Bay Area" and "47" in the codebase and consider replacing it w/ values that aren't hard-coded.