Augmentation to the simulation API response

[ScottLindley]

Hello! I see in server/handler/simulate.go that the SimulationResponse is a subset of common.Response. Is there any reason to not include all the data within common.Response? Would a PR that augmented SimulationResponse to be a 1:1 DTO mapping of common.Response be welcomed?

policy-bot/server/handler/simulate.go

Lines 37 to 45 in bbf6336

	// SimulationResponse is the response returned from Simulate, this is a trimmed down version of common.Result with json
	// tags. This struct and the newSimulationResponse constructor can be extended to include extra content from common.Result.
	type SimulationResponse struct {
	Name string `json:"name"`
	Description string `json:"description:"`
	StatusDescription string `json:"status_description"`
	Status string `json:"status"`
	Error string `json:"error"`
	}

[bluekeyes]

I think the main reason these are different is that common.Result is used as both the overall result of evaluating a policy and as the individual result of each rule, while SimulationResult is only representing the top-level status of the policy. On a practical level, we also wanted to minimize the public surface of the API until we knew what was useful.

I'm not sure a full 1:1 mapping makes sense, but I'm definitely open to adding more fields if they would help. I'm also curious to know more about how you're using the simulation API, if you're willing to share.