feat: Allow differentiating V0 and V1 programmatically

[saltiyazan]

Description

Some requirers like Traefik need to support both V0 and V1, no to have two different relations for different implementations of the same interface we improve the library so the requirer can check if it is connecting to a provider that implements V0 or V1:

• Adds the V1 postfix to the Object identifier in V1 of the lib so the objects for both V0 and V1 can be created for the same relation name with no conflicts.
• Adds is_ready() functions to the require that allows the requirer to validate the relation data of the provide, if it passes the checks for V0 then the provider is implementing V0 if it passes the checks for V1 then the provider is implementing V1, then the requirer can run different code for different providers.

This will be used to address the comments in this PR in Traefik.

Checklist

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that validate the behaviour of the software.
• I validated that new and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.
• I have bumped the version of any required library.