feat: add initialOffset for OffsetQueryPagingSource

[MohamadJaara]

Introduces initialOffset parameter to OffsetQueryPagingSource, allowing consumers to set a custom starting point. Enhances flexibility and control over data retrieval.

[hfhbd]

@MohamadJaara Please run ./gradlew spotlessApply

[hfhbd]

These changes will break the ABI. Are we okay with it due to the status of this module? Or do we need a binary compatibility overload?

[MohamadJaara]

@hfhbd i added new functions with the initial value hopfully this will be fine

[AlecKazakova]

I assume we want a default param for initialOffset anyways which we could @jvmoverloads to get binary compatibility

[MohamadJaara]

@AlecKazakova do you mean for the OffsetQueryPagingSource class something like

internal class OffsetQueryPagingSource<RowType : Any> @JvmOverloads constructor (
    private val queryProvider: (limit: Int, offset: Int) -> Query<RowType>,
    private val countQuery: Query<Int>,
    private val transacter: TransacterBase,
    private val context: CoroutineContext,
    private val initialOffset: Int = 0,
) : QueryPagingSource<Int, RowType>() {

or for the functions

@Suppress("FunctionName")
@JvmName("QueryPagingSourceInt")
@JvmOverloads
fun <RowType : Any> QueryPagingSource(
  countQuery: Query<Int>,
  transacter: TransacterBase,
  context: CoroutineContext,
  queryProvider: (limit: Int, offset: Int) -> Query<RowType>,
  initialOffset: In = 0,
): PagingSource<Int, RowType> = OffsetQueryPagingSource(
  queryProvider,
  countQuery,
  transacter,
  context,
  initialOffset,
)

[AlecKazakova]

for ABI compatibility we would need both

[JakeWharton]

The constructor does not need overloads because nobody except our own code is referencing it.

[AlecKazakova]

cool, just the methods then