Make product availability more clear

[zostay]

The checks and exes that was there before was unclear. This is more obvious at a glance.

[Copilot]

Pull Request Overview

This PR improves the visual clarity of product availability across different regions by replacing text-based checkmarks and X symbols with colored emoji indicators in a documentation table.

• Replaces ✓ (checkmark) and ✗ (X) symbols with 🟢 (green circle) and 🔴 (red circle) emojis
• Makes product availability status more visually distinct and accessible at a glance

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Using only colored emojis to convey availability status may create accessibility issues for users with color blindness or screen readers. Consider adding text labels or using symbols that don't rely solely on color differentiation.

Suggested change

	| GPU Compute | 🟢 | 🟢 | 🔴 | 🔴 | 🔴 | 🔴 |
	| CPU Kubernetes | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available |
	| CPU Compute | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available |
	| Object Stores | 🟢 Available | 🔴 Unavailable | 🟢 Available | 🟢 Available | 🔴 Unavailable | 🟢 Available |
	| Volumes | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available |
	| Machine Learning | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available |
	| Databases | 🟢 Available | 🔴 Unavailable | 🟢 Available | 🟢 Available | 🟢 Available | 🟢 Available |
	| GPU Kubernetes | 🟢 Available | 🟢 Available | 🔴 Unavailable | 🔴 Unavailable | 🔴 Unavailable | 🔴 Unavailable |
	| GPU Compute | 🟢 Available | 🟢 Available | 🔴 Unavailable | 🔴 Unavailable | 🔴 Unavailable | 🔴 Unavailable |

[zostay]

I had thought of the accessibility issue. The solution proposed by copilot highlights the issue, but doesn't solve it very well. For that, I'd suggest switching to an HTML table and attaching proper ARIA tags to the documentation, but that's out of scope. I'm just intending to make this more obvious to a visual user. I completely missed that Object Store was not available in PHX1 because the exes are not visually very different from the checks in the font used by the Civo docs site.