Remove round corner for search inputs

[CPerinet]

Checklist

• Includes tests
• Update documentation

Changes proposed in this pull request:

Remove the rounded corners of search inputs.

Screenshot

[changelog-app]

Generate changelog in packages/core/changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Remove round corner for search inputs

Check the box to generate changelog(s)

• Generate changelog entry

[svc-palantir-github]

Remove round corner for search inputs

Build artifact links for this commit: documentation | landing | table | demo

This is an automated comment from the deploy-preview CircleCI job.

[CPerinet]

@adidahiya

There are instances when the round corner looks off — typically when placed next to a square-er component such as Button. As a result, the default input is used in many instances instead of the type="search". Thus, we lose the semantic and esc behaviour.

I appreciate that, with this change, there is not much in the way of telling a search input from a default input. The way I see it being done is through icon="IconNames.SEARCH" and placeholder="Search...". Maybe we could set those as default for the search input?