Consider removing Deleter interface and always use .=id=X to delete item

[maksym-nazarenko]

It looks like that =numbers=X is a convenience way to delete items not only by ID, but also by name, id, etc.
As we moving forward with new interface-based implementation for all client resources, we could consider always using item's .id field to remove it.

It would simplify logic and remove some unnecessary code.

Find<ResourceName>() functions in client would need to be updated to Find<ResourceName>ByName() (in case of name attribute) so underlying helper function will:

1. Find the remote MikroTik object by its field.
2. Get .id from the record and call Delete() generic method.

However, it will still be possible to delete particular instance of the object, if you have one, e.g:

c := NewClient(GetConfigFromEnv())
list, _ := c.FindInterfaceList("list_name")
c.Delete(list)

TODO:

• Check if all tests pass in case of the change

@ddelnano wdyt?

[maksym-nazarenko]

@ddelnano I updated all client tests to use generic client.Delete(...) function which accepts Resource interface and uses .id field to delete RouterOS resource and everything worked.

One thing I noticed was that we have delete functions accepting other unique identifiers like name, e.g. c.DeleteInterfaceList("list-name") so changing those functions to accept id field would break the things.

At this moment I am not sure if it is feasible to proceed with this change and we can leave it as-is as it brings no benefits 🤷
wdyt?