Proposal: `Annotation.userInfo` should be non-optional

The current Annotation protocol defines userInfo as [String: Any]?

This can encourage some subtle bugs:

struct Polyline {
    var userInfo: [String: Any]?
}

// Assigning to nil
var foo = Polyline()
foo.userInfo?["test"] = 1

print(foo.userInfo ?? "Missing") // "Missing"

// Easiest solution
foo.userInfo = ["initial": "value"]
foo.userInfo = ["test": 1] // This will override any existing values

print(foo.userInfo ?? "Missing") // "["test": 1]" The initial value is missing

// More correct solution
foo.userInfo = foo.userInfo ?? [:]
foo.userInfo?["new"] = "value"

print(foo.userInfo ?? "Missing") // "["test": 1, "new": "value]"

Making userInfo non-optional would not entirely remove the possibility of bugs, but it would reduce the likelihood and make code much simpler.

Start with the Annotation protocol declaration in Sources/MapboxMaps/Annotations/AnnotationOrchestrator.swift at line 13, then trace the affected Annotation conformers. Determine the required API and implementation changes so userInfo is non-optional; the issue is complete when annotations can update userInfo without optional initialization or replacement pitfalls.