Alerting: Fix per-receiver RBAC for receivers with long names (#95084)

* Implement uidToResourceID

* add middleware

* Move uidToResourceID to alerting package

* Only hash uid if it's too long

* Use hashed uid in access control

* Move ReceiverUidToResourceId to ScopeProvider

* resolve uid in middleware only if param exists

* Tests

* Linting

---------

Co-authored-by: Yuri Tseretyan <yuriy.tseretyan@grafana.com>

pkg/tests/apis/alerting/notifications/receivers/receiver_test.go

@@ -481,6 +481,14 @@ func TestIntegrationAccessControl(t *testing.T) {
 		)...),
 	})
 
+	// Test receivers with uids longer than 40 characters. User name is used in receiver name.
+	adminLikeUserLongName := helper.CreateUser("adminLikeUserCreatingAReallyLongReceiverName", apis.Org1, org.RoleNone, []resourcepermissions.SetResourcePermissionCommand{
+		createWildcardPermission(append(
+			[]string{accesscontrol.ActionAlertingReceiversCreate},
+			ossaccesscontrol.ReceiversAdminActions...,
+		)...),
+	})
+
 	// endregion
 
 	testCases := []testCase{
@@ -555,6 +563,15 @@ func TestIntegrationAccessControl(t *testing.T) {
 			canAdmin:       true,
 			canReadSecrets: true,
 		},
+		{
+			user:           adminLikeUserLongName,
+			canRead:        true,
+			canCreate:      true,
+			canUpdate:      true,
+			canDelete:      true,
+			canAdmin:       true,
+			canReadSecrets: true,
+		},
 	}
 
 	admin := org1.Admin