refactor(1-1-restore): refactors 1-1-restore progress

[VAveryanov8]

This refactors 1-1-restore progress to address code review comments from #4296 by making following changes:

• include nodetool refresh into table progress
• only track progress of table/view restore
• removes unnecessary stats (shard_count, host bandwidth, aggregation by
  host, keyspaces). These stats are better to keep in metrics or
  calculate on the client side.

Now getProgress api response will have following structure:

{
  "tables": [
    {
      "started_at": "2025-01-01T12:00:01Z",
      "completed_at": "2025-01-01T12:00:03Z",
      "size": 20,
      "restored": 20,
      "status": "done",
      "keyspace": "ks1",
      "table": "t2"
    },
    {
      "started_at": "2025-01-01T12:00:00Z",
      "completed_at": null,
      "size": 40,
      "restored": 40,
      "status": "in_progress",
      "keyspace": "ks1",
      "table": "t1"
    }
  ],
  "views": [
    {
      "started_at": "2025-01-01T12:00:01Z",
      "completed_at": null,
      "size": 0,
      "restored": 0,
      "status": "in_progress",
      "keyspace": "ks1",
      "table": "v1",
      "type": "MaterializedView"
    },
    {
      "started_at": "2025-01-01T12:01:03Z",
      "completed_at": "2025-01-01T12:00:04Z",
      "size": 0,
      "restored": 0,
      "status": "done",
      "keyspace": "ks1",
      "table": "v2",
      "type": "MaterializedView"
    }
  ]
}

status field is introduced to better cover cases when we can't say if restore operation of table/view is complete just by looking at size and restored, because for tables we need to wait until nodetool refresh is complete and for views - until view rebuild operation is complete.

Refs: #4205

---

Please make sure that:

• Code is split to commits that address a single change
• Commit messages are informative
• Commit titles have module prefix
• Commit titles have issue nr. suffix

[karol-kokoszka]

@VAveryanov8 please pull from the feature branch (or git stash your commits before, and git stash pop after pulling them)

[Copilot]

Copilot reviewed 39 out of 51 changed files in this pull request and generated no comments.

Files not reviewed (12)

• pkg/service/one2onerestore/testdata/1.run_table_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/1.run_view_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/2.run_table_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/2.run_view_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/3.run_table_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/3.run_view_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/4.run_table_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/4.run_view_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/5.run_table_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/5.run_view_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/6.run_table_progress.json: Language not supported
• pkg/service/one2onerestore/testdata/6.run_view_progress.json: Language not supported

Comments suppressed due to low confidence (3)

pkg/service/one2onerestore/progress.go:296

• The mergeProgressStatus function returns 'in_progress' when merging differing statuses (except if one is 'failed'). Please verify that this behavior is intended for cases where one progress might already be 'done'.

func mergeProgressStatus(dst, src ProgressStatus) ProgressStatus {

pkg/service/one2onerestore/model.go:75

• [nitpick] Consider renaming 'scyllaTableWithSize' to a more descriptive name such as 'tableToRestore' to clarify its role in tracking table sizes for restoration.

tablesToRestore []scyllaTableWithSize

pkg/service/one2onerestore/progress.go:9

• [nitpick] Consider renaming the alias 'stderr' for the standard errors package to something more descriptive like 'stdErrors' to avoid potential confusion.

stderr "errors"