Add NoDataAlert widget

[Clebal]

Story details: https://app.shortcut.com/cartoteam/story/183641

[shortcut-integration]

This pull request has been linked to Shortcut Story #183641: Add component for showing an alert in widgets when there is no data available.

[coveralls]

Pull Request Test Coverage Report for Build 1295492895

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.1%) to 74.407%

---

Totals
Change from base Build 1291465225:	-0.1%
Covered Lines:	695
Relevant Lines:	866

---

💛 - Coveralls

[VictorVelarde]

I've added it also to FormulaWidget, for consistency (and because default 0.00 value for empty might be wrong / misleading under certain operations). I also reduced a bit the IMO very long text (@borja-munoz can maybe give us feedback on that during QA)

[VictorVelarde]

LGTM, so 🚀

[Clebal]

Sorry @VictorVelarde, I don't agree. From my experience in PS projects, when the count of elements is 0, the client wants to see 0, no "No data". That's why I didn't add it there.

Another example, if the sum of revenue of a certain store is 0, it isn't the same as no data.

Maybe I'd add it when formulaData is null or undefined.

[VictorVelarde]

I understand that displaying 0.0 might be fine assuming Count or Sum, but there are other operations that can be applied to Formula, where 0 is not, IMO, correct. Having said that I have no issues in reverting that commit, let's just ping @borja-munoz for confirmation on this before merging it

[VictorVelarde]

I'm gonna do one thing, I'm gonna revert my commit 0d021bf, so to merge this as Sergio set it, and if Borja wants to include my FormulaWidget change, we can do another PR with cherry-pick later

[borja-munoz]

I think for COUNT operations makes sense to show 0 if there is no data in the current viewport. For the other aggregation operations (SUM, AVG, MIN, MAX), I think it is better to show the no data message.

Sorry for introducing a third option. If there is no time now to implement it, I'd keep Sergio's approach for now, but revisit this in the future.