member information is duplicated in `users.members` and `user_memberships` table.

[Psi]

users.members is a boolean, while the user_memberships table is associated to stripe subscriptions.

I'm guessing that users.member is meant to capture old members from before the transition to user-api. However it's got no time frame associated with it so we should probably just use the user_memberships table.

Edit: to clarify it looks like users.member table is a check to verify that a user is a music making member. Again, this probably should be automatically calculated based on if someone has just uploaded a track to Resonate (which is what it does in that migration script), rather than stashed.

But since there's no way to manually keep track of worker members (except for on the Discourse) we can keep the user.member column and use it for that. The other two memberships should be calculated automatically though.

[Psi]

we decided that the members column was legacy information that we would keep toggled for now, but that we would eventually use it to indicate worker members.