Add ext3 and xfs fsTypes to e2e format-option test coverage

[AndrewSirenko]

Is this a bug fix or adding new feature?
Test coverage

What is this PR about? / Why do we need it?
Adds ebscsidriver.FSTypeExt3 and ebscsidriver.FSTypeXfs as tested filesystems for our e2e format option tests.

This is separate from turning on the ext3 feature flag for upstream k8s storage conformance tests. See #1891 for that.

This is separate from the discussion of whether we are deprecating support for ext2

This would add the following tests:

[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext3 filesystem with a custom blocksize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext3 filesystem with a custom bytesperinode parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext3 filesystem with a custom inodesize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext3 filesystem with a custom numberofinodes parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an xfs filesystem with a custom blocksize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an xfs filesystem with a custom inodesize parameter successfully mounts and is resizable

(Note, not all formatting-option parameters that are supported for ext4 are supported for ext3 and xfs. See pkg/driver/constants.go)

What testing is done?
Manually running the new ext3 and xfs format option tests. Here is a list of those tests.

❯ ginkgo run --focus 'format-options' --dry-run -v | grep -i "az"
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext3 filesystem with a custom blocksize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext3 filesystem with a custom bytesperinode parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext3 filesystem with a custom inodesize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext3 filesystem with a custom numberofinodes parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext4 filesystem with a custom blocksize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext4 filesystem with a custom bytesperinode parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext4 filesystem with a custom ext4bigalloc parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext4 filesystem with a custom ext4clustersize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext4 filesystem with a custom inodesize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an ext4 filesystem with a custom numberofinodes parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an xfs filesystem with a custom blocksize parameter successfully mounts and is resizable
[ebs-csi-e2e] [single-az] [format-options] Formatting a volume using an xfs filesystem with a custom inodesize parameter successfully mounts and is resizable

[github-actions]

Code Coverage Diff

This PR does not change the code coverage

[ConnorJC3]

/lgtm

[torredil]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: torredil

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [torredil]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment