fix: data.property.planning type should use more precise language

[jessicamcinchak]

Changes:

• intersects instead of overlaps to match actual spatial method used (eg DE-9IM definition)
• adds source where we'll send Planx GIS API request to enable re-fetching, but another provided could put any URL
• breaks down constraints into more specific groupings per advice from Alastair & Emily (see thread)
  • any mix of various constraint categories can be sent, a source is required if sending any category
  • the specific keys of designations & orders have expected enums, but others are currently flexible as Planx won't fulfill these yet

  /**
   * @description Planning constraints and policies that intersect with this site and may impact or restrict development
   */
  planning?: {
    /**
     * @description An open API request or website that explains how these constraints were sourced
     */
    source: URL;
    designations?: PlanningDesignation[];
    orders?: PlanningOrder[];
    conditions?: PlanningConstraint[];
    guidance?: PlanningConstraint[];
    plans?: {
      local: PlanningConstraint[];
      neighbourhood: PlanningConstraint[];
    };
  };