Adds fields to Asset model as per asset registration v2

[rithviknishad]

Closes #3426
as part of #2212

In the Asset Create/Update and Asset Detail page:

• Renamed "Phone No" as "Customer support No."
• The following fields were added in the Asset Create/Update and Asset Detail page

1: Manufacturer: Short text field, optional
2: Warranty/AMC applicable till: Date, Optional
3: Last serviced on: Date- Optional
4: Notes: Long text field- optional

• Field warranty_details removed from the Asset Create/Update and Asset Detail

Additional changes:

• Implements hook: useVisibility

  Usage Example:

  const [isVisible, elementRef] = useVisibility(-200);
  
  useEffect(() => {
      // do something.
  }, [isVisible]);
  
  return (
      ...
      <Element ref={elementRef} />
      ...
  );

• Implemented Tailwind component: TextInputFieldV2
  

  Usage example:

  {/* Asset Name */}
  <div className="col-span-6 sm:col-span-4">
    <TextInputFieldV2
      id="asset-name"
      label="Asset Name"
      value={name}
      onValueChange={setName}
      error={state.errors.name}
      required
    />
  </div>

• Updated Tailwind component: SelectMenu with new design
  Also fixed it's overflow issues.
  

  Usage Example:

  {/* Asset Type */}
  <div className="col-span-6 sm:col-span-2">
    <label htmlFor="asset-type">Asset Type * </label>
    <div className="mt-2">
      <SelectMenuV
        options={[
          {
            title: "Select",
            description:
              "Select an Asset Type from the following",
            value: undefined,
          },
          {
            title: "Internal",
            description:
              "Asset is inside the facility premises.",
            value: "INTERNAL",
          },
          {
            title: "External",
            description:
              "Asset is outside the facility premises.",
            value: "EXTERNAL",
          },
        ]}
        selected={asset_type}
        onSelect={setAssetType}
      />
    </div>
    <ErrorHelperText error={state.errors.asset_type} />
  </div>

• Implemented Tailwind component RadioInputsV2
  

  Usage example:

  {/* Working Status */}
  <RadioInputsV2
    className="col-span-6"
    required
    label="Working Status"
    name="is_working"
    options={[
      { label: "Working", value: "true" },
      { label: "Not Working", value: "false" },
    ]}
    selected={is_working}
    onSelect={setIsWorking}
    error={state.errors.is_working}
  />

• Implemented Tailwind Component SwitchV2
  

  {/* Working Status */}
  <SwitchV2
    className="col-span-6"
    required
    name="is_working"
    label="Working Status"
    options={["true", "false"]}
    optionLabel={(option) => {
      return (
        {
          true: "Working",
          false: "Not Working",
        }[option] || "undefined"
      );
    }}
    optionClassName={(option) =>
      option === "false" &&
      "bg-error text-white border-error focus:ring-error"
    }
    value={is_working}
    onChange={setIsWorking}
    error={state.errors.is_working}
  />

[netlify]

✅ Deploy Preview for care-egov-staging ready!

Name	Link
🔨 Latest commit	5d4c43a
🔍 Latest deploy log	https://app.netlify.com/sites/care-egov-staging/deploys/6332dfed06817800081b62bf
😎 Deploy Preview	https://deploy-preview-3458--care-egov-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[mathew-alex]

👋 Hi, @rithviknishad,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.4% Duplication

[nihal467]

@rithviknishad In the weekly call, we discussed about the two scroller been coming out in the asset creation page, are you working on it now or will it be a another PR coming after this one is merged !

[rithviknishad]

@nihal467 I'll make it as another PR then, since this PR has lot's of changes, its getting merge conflicts pretty quickly.

[nihal467]

@rithviknishad

i feel like the card is little bit towards down, shall we move a bit up, just an opinion, what do you think,

[nihal467]

@rithviknishad @khavinshankar seem like a small alignment issue, we can work on another PR, this LGTM,

[khavinshankar]

@rithviknishad the ui looks awesome, and if you have time do refactor classname using clsx which improves the readability, I'm merging this, so pick it up as a new pr