Bug: load correct workflow page on initial render

[emma-sg]

Fixes #2676
cc @SuaYoo

Changes

• Only resets page to 1 when switching filters after initial load
• Always renders <btrix-pagination> so that page changes are always reflected in the URL

Testing

Tested locally, it seems to work

[SuaYoo]

I still see pagination issues with the following steps on "Default Org":

1. Go to /workflows?page=3
2. Change sort
3. Check network log. Page is reset to 1 but pagination remains 3

I think a simpler fix might be to move fetchWorkflows to the firstUpdated callback and switch the changedProperties.has to changedProperties.get. I'll do some more testing but this should work:

  protected async willUpdate(
    changedProperties: PropertyValues<this> & Map<string, unknown>,
  ) {
    if (
      changedProperties.get("orderBy") ||
      changedProperties.get("filterByCurrentUser") ||
      changedProperties.get("filterByScheduled") ||
      changedProperties.get("filterBy")
    ) {
      void this.fetchWorkflows({ page: 1 });
    }
    if (changedProperties.has("filterByCurrentUser")) {
      window.sessionStorage.setItem(
        FILTER_BY_CURRENT_USER_STORAGE_KEY,
        this.filterByCurrentUser.toString(),
      );
    }
  }

  protected firstUpdated() {
    void this.fetchWorkflows({
      page: parsePage(new URLSearchParams(location.search).get("page")) || 1,
    });

    void this.fetchConfigSearchValues();
  }

[emma-sg]

I think a simpler fix might be to move fetchWorkflows to the firstUpdated callback

I think this works too, but I'd rather kick off the data fetch a little earlier in the component lifecycle: in the future if/when I get fetch caching working, this'll prevent an initial render without data when data is cached.