ManageIncidentsOptions doesn't take EscalationLevel

[sim1s]

While trying to use the go-pagerduty client to escalate an incident, I noticed that EscalationLevel is missing in ManageIncidentsOptions

go-pagerduty/incident.go

Lines 169 to 177 in 340f6d5

	type ManageIncidentsOptions struct {
	ID string `json:"id"`
	Type string `json:"type"`
	Status string `json:"status,omitempty"`
	Priority *APIReference `json:"priority,omitempty"`
	Assignments []Assignee `json:"assignments,omitempty"`
	EscalationPolicy *APIReference `json:"escalation_policy,omitempty"`
	Resolution string `json:"resolution,omitempty"`
	}

The payload for the API allows for escalation_level

https://developer.pagerduty.com/api-reference/reference/REST/openapiv3.json/paths/~1incidents/put

[theckman]

@sim1s do you know whether that field uses zero-based indices? They don't show an example, so I'm not sure if the second escalation level is 1 or 2. Also, might you have the spare cycles to raise a PR to add this?

For some context, this library is largely community maintained, and while I can review and merge PRs contributed by others I cannot merge my own and must wait for a PD employee to have some time to review my changes.

If you had the time to raise the PR and address any feedback, it would make it so I could merge it in to eventually be released with v1.5.0.

[sim1s]

@theckman the field does not use zero-based indices, the first escalation level is 1. The response also does not specify which escalation level is currently triggered, and sending a value of 0 or 1 brings the escalation down to the lowest level (first responders).

Here's a PR to resolve this