[Dashboards in Chat] Additional guidance to agents regarding tables

Add this guidance to both:
- [ ] Agent Builder in Kibana
- [ ] 3rd party skill

**Tables guidance:**
- [ ] Only apply **colour badges to metrics** (NOT categorical values) when 1) the metric has a fixed direction (either high or low is bad) e.g. errror rate, latency, CPU, etc. OR 2) there's a threshold e.g. SLA, etc. Metrics like average order size, session count, or number of tickets don't have an inherent good side so don't colour them.
- [ ] Pick only **1 column to colour** (not multiple), the metric that actually drives a decision (sometimes this is the columns that sorts the table) and leave the rest neutral so it can act as context.
- [ ] You can **optionally** use **progress bars** in tables (badges should be more common than progress bars). Use them only for 1 of the columns, pick the most important one. Use them only when there is one metric in the table that has a real ceiling for example metrics related with resource saturation: disk, memory, heap, CPU, etc. 100% is a physical limit and a known failure mode. Use the default colour palette (gradient and status palette) as shown in this picture:

**Combining**
- Don't apply any cell decoration by default if you don't have a metric that meets the criteria above
- Never combine progress bars with badges in the same table
- At most 1 decorated column per table
- Never decorate a column the row is grouped by, or an identifier column.

**Related issue**

When the Agent uses gradient scales for badges, they sometimes appear blank like int he video below. Fix this problem as part of this issue too.