Do not complain about EO in POD

[bschmalhofer]

The convention is to use EO in change markers when a package overrides a package in OTOBO core. This change marker can also be used in POD. CodePolicy should not complain about it.

=head2 CalendarUpdate()

updates an existing calendar.

    my $Success = $CalendarObject->CalendarUpdate(
        CalendarID       => 1,                   # (required) CalendarID
# RotherOSS / TicketIcalIntegration
#       GroupID          => 2,                   # (required) Calendar group
        GroupID          => 2,                   # GroupID or OwnerID is required
        OwnerID          => $UserID,
# EO TicketIcalIntegration
        CalendarName     => 'Meetings',          # (required) Personal calendar name
        Color            => '#FF9900',           # (required) Color in hexadecimal RGB notation
        UserID           => 4,                   # (required) UserID (who made update)
        ValidID          => 1,                   # (required) ValidID

        TicketAppointments => [                 # (optional) Ticket appointments, array ref of hashes
            {
                StartDate => 'FirstResponse',
                EndDate   => 'Plus_5',
                QueueID   => [ 2 ],
                RuleID    => "363665b0ad6b1a7d14a9a30354e80c60",
                SearchParams => {
                    Title => 'This is a title',
                    Types => 'This is a type',
                },
            },
        ],
    );

Returns 1 if successful.

Events:
    CalendarUpdate

=cut

[bschmalhofer]

The fix is pushed to the internal repository. Let's wait and see whether the commit makes the trip to the public Github.