Create Logs and Error Types as part of the ipyleaflet Map Object

[sandrahoang686]

Description

It would be helpful to collect logs and errors during runtime and make them available to access as part of the ipyleaflet map object. Therefore users can access logs and errors at anytime whenever needed.

This issue should just create the standard and have a few use cases in certain areas. The use cases will grow as more features are developed.

Acceptance Critieria

• Define what types of logs we would care to collect and document this in-code
• Create a log & error class type to create standardization here
• Use the logging whenever we would want to report to the user right away, otherwise push these logs/errors to the Map object (usecases include in the collections logic, whenever a collection is skipped due to being non-compliant, we should collect and add as a log to the Map Object)
• To do this, we would need to make the Map object accessible wherever there are possible logs to collect. A possible solution might be to... create a log/error class that extends the Map object

class Logs(TypedDict):
    error: bool // error or log?
    message: str // custom message
    raw_error: str // possible stack trace
    metadata: Optional[Dict[str, str]]


class LogsAndErrorCollections(StacIpyleaflet):
....