Add Tags sections to Stories, CommunityNews, Events, and Resources edit pages

[Copilot]

What is the goal of this PR and why is this important?

Stories, CommunityNews, Events, and Resources edit pages lacked UI for assigning categories and sectors, despite models already having the necessary associations and TagFilterable concern. This adds the missing UI following the Workshop edit page pattern.

How did you approach the change?

Controllers (stories, community_news, events, resources):

• Added assign_associations method to convert checkbox params to ActiveRecord associations
• Wrapped create/update in transactions to ensure atomicity with tag assignments
• Extended set_form_variables to load @sectors and @categories_grouped
• Added category_ids: [] and sector_ids: [] to strong params

Views (_form.html.erb for each resource):

• Added collapsible Tags accordion with Service Populations (sectors) and Additional Tags (categories grouped by type)
• Used checkbox arrays with hidden fields to handle unchecked state
• Matched Workshop's UI structure and styling exactly

def assign_associations(story)
  selected_category_ids = Array(params[:story][:category_ids]).reject(&:blank?).map(&:to_i)
  story.categories = Category.where(id: selected_category_ids)

  selected_sector_ids = Array(params[:story][:sector_ids]).reject(&:blank?).map(&:to_i)
  story.sectors = Sector.where(id: selected_sector_ids)
end

Anything else to add?

Resources controller already permitted tag params but lacked the assignment logic and form UI. No model changes required - all associations were already configured.

Original prompt

add Tags section to edit page for: Stories, CommunityNews, Events, Resources, if not already present. follow the pattern established in the Workshop edit.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.