ERC721Consecutive batch minting not enabled after construction

[arr00]

🧐 Motivation
The current implementation for ERC721Consecutive implements ERC-2309, enabling batch mints during the construction of the token; however, there are many use cases that require batch minting after construction. ERC721Consecutive falls back to a single mint function.

📝 Details

openzeppelin-contracts/contracts/token/ERC721/extensions/ERC721Consecutive.sol

Lines 109 to 111 in 450b833

	if (address(this).code.length > 0) {
	revert ERC721ForbiddenBatchMint();
	}

[ernestognw]

Concretely, this feature may be implemented as:

if (address(this).code.length > 0 && !NON_COMPLIANT_ALLOW_BATCH_MINT_AFTER_CONSTRUCTION()) {
    revert ERC721ForbiddenBatchMint();
}

...

/// @dev <some comment explaining devs can turn this on, but it would make the constract non ERC721 compliant
function NON_COMPLIANT_ALLOW_BATCH_MINT_AFTER_CONSTRUCTION() internal pure virtual returns (bool) { return false; }

So that developers can customize with:

function ALLOW_BATCH_MINT_AFTER_CONSTRUCTION() internal pure override returns (bool) { return true; }

[Amxx]

One of the risks that has to be considered/documented is that the range of batch mint done after construction may overlap with tokenIds minted using the "tranditional" _mint function. In that case we need to understand and document the behavior.