feat: `lock()` accepts a `userId` param if it's required to complete the login

[palazzem]

Related Issues

• Related to #123

Proposed Changes:

This change adds support for all main units that require a userId parameter, such as the ETR128.

When the system is armed and disarmed, the AlarmDevice splits and sends the userId and the code if they are both required by the main unit. The login_without_user_id value from the panel details defines if the unit requires it or not.

In case the userId is not required, that parameter is not sent. If panel details are not available, the device assumes it's not needed (true for most recent main units).

Users can insert both code directly from the alarm panel simply combining first the userId and then the code.

Example:

• User: 010
• Code: 987654
• You should input in the alarm panel: 010987654

Testing:

n/a

Extra Notes (optional):

n/a

Checklist

• [x] Related issues and proposed changes are filled
• [x] Tests are defining the correct and expected behavior
• [x] Code is well-documented via docstrings

[coveralls]

Pull Request Test Coverage Report for Build 7783559573

• 0 of 17 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.2%) to 93.83%

---

Totals
Change from base Build 7759757295:	0.2%
Covered Lines:	620
Relevant Lines:	664

---

💛 - Coveralls