Support annotation view lookup by id.

[maios]

• Allow adding annotation view with a custom id, that can be used later to look it up.

Pull request checklist:

• Describe the changes in this PR, especially public API changes.
• Write tests for all new functionality. If tests were not written, please explain why.
• Add documentation comments for any added or updated public APIs.
• Add a changelog entry to to bottom of the relevant section (typically the ## main heading near the top).

PRs must be submitted under the terms of our Contributor License Agreement CLA.

[evil159]

I wonder if we should add a convenience method to update(remove to a lesser extent as well) a view annotation with id now when we allow passing custom id when adding a view annotation.
This change is requested in the context of making it easier to change a view annotation, so this addition, while being very cheap to us, might make this use case a bit more convenient.
E.g.:

// it is possible to get a view and update options for it currently
if let view = view(forId: id) {
    manager.update(view, options)
}

// with a convenience method this could be a single invocation
manager.update(forId: id, options)

// the convenience method
public func update(forId id: String, options: ViewAnnotationOptions) throws {
    guard let view = view(forId: id) else {
          throw ViewAnnotationManagerError.annotationNotFound
    }

    update(view, options: options)
}

[maios]

I wonder if we should add a convenience method to update(remove to a lesser extent as well) a view annotation with id now when we allow passing custom id when adding a view annotation. This change is requested in the context of making it easier to change a view annotation, so this addition, while being very cheap to us, might make this use case a bit more convenient. E.g.:

// it is possible to get a view and update options for it currently
if let view = view(forId: id) {
    manager.update(view, options)
}

// with a convenience method this could be a single invocation
manager.update(forId: id, options)

// the convenience method
public func update(forId id: String, options: ViewAnnotationOptions) throws {
    guard let view = view(forId: id) else {
          throw ViewAnnotationManagerError.annotationNotFound
    }

    update(view, options: options)
}

I wanted to do the same, but I want to clarify some design intention behind the current ViewAnnotationsManager/update(_:options:) to accept new options with same associatedFeatureId (currently we don't accept it, so new associatedFeatureId has to be either nil or different value), after this we might want to change the current implementation so I want to cut it to another ticket.

[MICHELLGRONER88]

#581 @sandeep-mapbox

[MICHELLGRONER88]

snapcodes.zip