fix: chain filter does not update last_active

[kenjis]

Description
Fixes #1154

The chain filter also should update last_active.

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[datamweb]

This feature only works when session/tokens filter is active.

shield/src/Config/Auth.php

Lines 157 to 167 in 0ead2a1

	/**
	* --------------------------------------------------------------------
	* Record Last Active Date
	* --------------------------------------------------------------------
	* If true, will always update the `last_active` datetime for the
	* logged-in user on every page request.
	* This feature only works when session/tokens filter is active.
	*
	* @see https://codeigniter4.github.io/shield/quick_start_guide/using_session_auth/#protecting-pages for set filters.
	*/
	public bool $recordActiveDate = true;

[warcooft]

@kenjis said: Yes,chain uses either session or tokens or hmac by default.

chain
The filter will check authenticators in sequence to see if the user is logged in through either of authenticators, allowing a single API endpoint to work for both an SPA using session auth, and a mobile app using access tokens.
https://shield.codeigniter.com/references/controller_filters/?h=chain#provided-filters

[kenjis]

@datamweb The option is used in HmacAuth, JWTAuth, SessionAuth, and TokenAuth filters.
Find 'Auth.recordActiveDate' in the source code.

Updated the comment for $recordActiveDate.

[datamweb]

@warcooft Thank you for your participation.
@kenjis Yes, the text should have been updated.

LGTM!