feat(contact-point): support retrieval by name

[Saurus119]

• Adds support for retrieving a contact point by its exact name.
• If multiple contact points share the same name, the method will return all matching contact points in a list.
• This can occur, for example, when an alert rule uses contact points that implement multiple actions. In Grafana’s UI, such contact points are grouped by name, but they are stored as separate contact points in the backend.

[Saurus119]

@ZPascal

[ZPascal]

Can you please contribute unit tests for the functionality?

[Saurus119]

Added, I also modified little bit existing test to get all:contact_points so it is crystal clear that it can return multiple, not only one.

• Modified get_contact_point because the response list() is valid response from the grafana API if you don´t have a match. So when you do call for the contact point that doesn´t exists you shouldn´t raise exception on empty list response.

[Saurus119]

• Maybe would be good to add functionality to create conditions as "Expressions". Based on your Models for alerts it doesnt exactly match the grafana API, for some functionality I had to just use your api_call and create payloads manually.

• Conditions (legacy) are pretty old and mostly when you have grafana sourced, you use "expressions", which is we can say condition but more smart. So maybe some "ExpressionCondition", where you can specify type as "Math", "Reduce", and so on would be nice to add and direclty use if you need. My usecase is: I created a queries to this queries I want to link Expressions where N of them are type of "Reduce" and one "Math" where I combine multiple conditions but I am not sure if you would welcome this functionality.