Are only standard-typed ACLs valid?

Hi there,

I noticed that ACL functions under module/acl.go only returns standard-typed ACLs. One such example can be seen in https://github.com/aristanetworks/goeapi/blob/master/module/acl.go#L161 . Device configs aren't often like this and many can have extended ACLs without any specified type, i.e. `ip access-list NAME` instead of `ip access-list standard NAME`, or `ip access-list payload NAME`.

Is the goeapi code just lacking support for non-standard ACL types (and if this is the case, would you be interested in PR to fix this?), or are general-typed ACLs the only thing you'll consider to be valid?

Start by reading module/acl.go around the ACL handling shown near line 161, then compare its behavior with the issue's examples: `ip access-list NAME` and `ip access-list payload NAME`. Done means the project’s supported ACL types are clarified and, if support is intended, those non-standard forms are handled consistently.

Written by the indexing model from the issue text.