2701: Separate schedule_upcall number and values through Rust types r=phil-levis a=alexandruradovici

### Pull Request Overview

This pull request groups the values returned by `schedule_upcall` into a tuple to prevent wrongly placing a value instead of the upcall number.

```rust
pub fn schedule_upcall(
        &self,
        subscribe_num: usize,
        r: (usize, usize, usize),
    ) -> Result<(), UpcallError> 
```

This tries to use Rust's type system to clearly separate the upcall number and the values. The `schedule_upcall` takes four `usize` parameters, the first one being the upcall number and the following three the values returned to the application. As all four parameters have the same type, it is easy to forget that the first parameter is the upcall number, not the first value. The compiler has no way of protecting against this error. 

This is inspired from the error within #2698.

There should be no impact in size or performance.

### Testing Strategy

N/A

### TODO or Help Wanted

N/A

### Documentation Updated

- [x] Updated the relevant files in `/docs`, or no updates are required.

### Formatting

- [x] Ran `make prepush`.


Co-authored-by: Alexandru Radovici <msg4alex@gmail.com>
Co-authored-by: Alexandru Radovici <alexandru.radovici@wyliodrin.com>

2698: Updated lps25hb to handle i2c errors r=bradjc a=Cristiana959

### Pull Request Overview

This pull request adds i2c error verification for the lps25hb drivers.

### Testing Strategy

This pull request was not tested as I do not own the sensor.


### TODO or Help Wanted

N/A


### Documentation Updated

- [x]  No updates required.

### Formatting

- [x] Ran `make prepush`.


Co-authored-by: Cristiana959 <cristiana699@gmail.com>
Co-authored-by: Cristiana Andrei <63002082+Cristiana959@users.noreply.github.com>

2701: Separate schedule_upcall number and values through Rust types r=phil-levis a=alexandruradovici

### Pull Request Overview

This pull request groups the values returned by `schedule_upcall` into a tuple to prevent wrongly placing a value instead of the upcall number.

```rust
pub fn schedule_upcall(
        &self,
        subscribe_num: usize,
        r: (usize, usize, usize),
    ) -> Result<(), UpcallError> 
```

This tries to use Rust's type system to clearly separate the upcall number and the values. The `schedule_upcall` takes four `usize` parameters, the first one being the upcall number and the following three the values returned to the application. As all four parameters have the same type, it is easy to forget that the first parameter is the upcall number, not the first value. The compiler has no way of protecting against this error. 

This is inspired from the error within tock#2698.

There should be no impact in size or performance.

### Testing Strategy

N/A

### TODO or Help Wanted

N/A

### Documentation Updated

- [x] Updated the relevant files in `/docs`, or no updates are required.

### Formatting

- [x] Ran `make prepush`.


Co-authored-by: Alexandru Radovici <msg4alex@gmail.com>
Co-authored-by: Alexandru Radovici <alexandru.radovici@wyliodrin.com>