ref(projects): Remove team data from deleted project audit

[macqueen]

depends on #6807

since projects will soon be able to be associated with multiple teams, i'm removing this data

[ghost]

	2 Warnings
⚠️	You should update CHANGES due to the size of this PR
⚠️	PR includes migrations

Migration Checklist

• new columns need to be nullable (unless table is new)
• migration with any new index needs to be done concurrently
• data migrations should not be done inside a transaction
• before merging, check to make sure there aren't conflicting migration ids

Generated by 🚫 danger

[mattrobenolt]

This will cause a problem since the columns will be removed while the code still is running referencing it. This needs to remove the columns from code first, then ship the migration to drop the columns after that's out.

[macqueen]

@mattrobenolt i did that as part of #6807 (a3e5145) which I was planning on merging first for that reason. buuut maybe it just makes more sense for me to pull that out into it's own PR since it doesn't have to be part of that. would that be better?

[mattrobenolt]

Oh, I see, then you're going to have a conflict here anyways. So we're good after #6807 merges. Your call if you want to split it out more or not, I don't personally think it's that important.

[macqueen]

ok @mattrobenolt this should be good to go now

[mattrobenolt]

You again need to recreate migration. :(

#6961