Support use of multiple eggplant suites

[Noordsestern]

Situation

Given the following test suite:

*** Settings ***
Library     EggplantLibrary    suite=${CURDIR}/eggplant/suite1.suite    AS    Suite1Library
Library     EggplantLibrary    suite=${CURDIR}/other_team/eggplant/suite2.suite    AS    Suite2Library


*** Test Cases ***
Demo
    Connect Sut    ${some_param}

Calling Connect Sut fails, because the keyword exists in both EggplantLibrary instances.

Expected

I would expect the static keywords to be available only once. I like to have the cusomt library names as domain prefixes for eggplant scripts:

*** Settings ***
Library     EggplantLibrary    suite=${CURDIR}/eggplant/suite1.suite    AS    DogLibrary
Library     EggplantLibrary    suite=${CURDIR}/other_team/eggplant/suite2.suite    AS    CatLibrary


*** Test Cases ***
Demo
    Connect SUT    ${some_param}
    DogLibrary.My eggplant Script
    CatLibrary.Other eggplant Script

[Noordsestern]

The requested feature is a bit more complex. The basic functionality is support for different eggplant suites that are not in same folders.

The use case behind this is cross-team collaboration. When team A is implementing eggplant tests for module 1 and team B for module 2, they may want to share their suites for some of their test cases.

I am about to provide a PR for this.