setup: devs can optionally just rely on biconomy_getUserOpStatus

[livingrockrises]

Summary

Related Issue: # (issue number)

Change Type

• Bug Fix
• Refactor
• New Feature
• Breaking Change
• Documentation Update
• Performance Improvement
• Other

Checklist

• My code follows this project's style guidelines
• I've reviewed my own code
• I've added comments for any hard-to-understand areas
• I've updated the documentation if necessary
• My changes generate no new warnings
• I've added tests that prove my fix is effective or my feature works
• All unit tests pass locally with my changes
• Any dependent changes have been merged and published

Additional Information

Branch Naming

[AmanRaj1608]

LGTM

[tomarsachin2271]

Give a default value of confirmations = 0 in the method

[AmanRaj1608]

the logic is already like this, so if confirmations is not defined or 0 it will just resolve and send back receipt

if (confirmations) {
  const latestBlock = await provider.getBlockNumber();
  const confirmedBlocks = latestBlock - userOpResponse.receipt.blockNumber;
  if (confirmations >= confirmedBlocks) {
    clearInterval(intervalId);
    resolve(userOpResponse);
  }
}

clearInterval(intervalId);
resolve(userOpResponse);

[tomarsachin2271]

Looks good

[AmanRaj1608]

Reverted the last commit as per discussion with @livingrockrises
The concern is user might not have the funding id in case of token paymaster and it will result in error.