Name and value of properties are missing on API

[mPokornyETM]

fix #595

Testing done

• an ephemeral resource 'testing' try to lock reserved resoure 'res1'
• the resource 'resource-with-properties' has 2 properties

Proposed upgrade guidelines

N/A

Localizations

N/N

Submitter checklist

• The Jira / Github issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).
  • The changelog generator for plugins uses the pull request title as the changelog entry.
  • Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during the upgrade.
• There is automated testing or an explanation that explains why this change has no tests.
• [ ] New public functions for internal use only are annotated with @NoExternalUse. In case it is used by non java code the Used by {@code <panel>.jelly} Javadocs are annotated.
• [ ] New or substantially changed JavaScript is not defined inline and does not call eval to ease the future introduction of Content Security Policy (CSP) directives (see documentation).
• [ ] For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.
  see Name and value of properties are missing on api #595
• [ ] Any localizations are transferred to *.properties files.
• Changes in the interface are documented also as examples.
  currently only this PR. We have no documentation for API at themoment.