feat(fusion_plating): kind.area_kind drives Shop Floor column routing

Add required area_kind Selection to fp.step.kind so each kind
self-declares which plant-view column its steps belong in. Replaces
the hardcoded _STEP_KIND_TO_AREA dict (removed in fp_job_step.py
in the follow-up commit).

- New `blast` kind for the Blasting column (sequence=35)
- 26 existing kind records seeded with area_kind in XML
- Pre-migrate 19.0.21.2.0 seeds existing rows BEFORE NOT NULL hits
  the schema; also activates derack/demask/gating that were
  deactivated in 19.0.20.6.0 but are needed for the full taxonomy
- Step Kind form + list views surface area_kind (badge + chip)
- Step Kind search adds Group By Shop Floor Column
- Simple Editor kind picker shows "Masking — Masking column"
  suffix so authors see the routing at pick time
- Add Hot Water Porosity Test (A-15) + Final Inspection / Packaging
  templates (used by 7+3 recipe nodes that previously had no
  library entry)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

fusion_plating/fusion_plating/views/fp_step_kind_views.xml

@@ -17,6 +17,7 @@
                 <field name="sequence" widget="handle"/>
                 <field name="name"/>
                 <field name="code"/>
+                <field name="area_kind" decoration-info="True"/>
                 <field name="icon"/>
                 <field name="template_count"/>
                 <field name="active" widget="boolean_toggle"/>
@@ -47,6 +48,8 @@
                     </div>
                     <group>
                         <group>
+                            <field name="area_kind" widget="badge"
+                                   help="Cards whose active step uses this kind appear in this column on the Shop Floor plant kanban."/>
                             <field name="sequence"/>
                             <field name="company_id"
                                    groups="base.group_multi_company"/>
@@ -94,8 +97,13 @@
             <search>
                 <field name="name"/>
                 <field name="code"/>
+                <field name="area_kind"/>
                 <separator/>
                 <filter string="Archived" name="inactive" domain="[('active','=',False)]"/>
+                <group>
+                    <filter string="Shop Floor Column" name="group_area_kind"
+                            context="{'group_by': 'area_kind'}"/>
+                </group>
             </search>
         </field>
     </record>