Switch Form Layout depending on screen size

[JasvinderSingh0309]

Description

Added a col-md-form-label class with breakpoint. Acts as form-label in small screens and col-form-label in larger screens. Has padding top and bottom in large screens and in small screens those padding is removed and margin bottom is added.

Motivation & Context

while using the col-form-label class instead of form-label causes and extra padding on the top.

Type of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (non-breaking change)
• Breaking change (fix or feature that would change existing functionality)

Checklist

• I have read the contributing guidelines
• My code follows the code style of the project (using npm run lint)
• My change introduces changes to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

Live previews

• https://deploy-preview-39874--twbs-bootstrap.netlify.app/

Related issues

[julien-deramond]

Thanks for submitting a PR @JasvinderSingh0309
I'm not sure if this is a feature that we would integrate by default in Bootstrap.
Anyway, this PR is incomplete:

• Lint issues
• @media shouldn't be used as is; the rest of the codebase is using @include media-* mixins.
• This new feature is not documented
• If such a feature would be implemented, it couldn't be just for the md breakpoint. It should work for all breakpoints.

[JasvinderSingh0309]

Thank you for the feedback on my pull request. As a beginner, I'm keen to improve. Could you share more detailed feedback? It will help me focus on areas for future contributions. Thanks for your time and guidance.

[julien-deramond]

Unfortunately, I'm working on Bootstrap on my spare time, and can't use this time to onboard someone on the technical aspects of the codebase, even if I would love it.

I will close this PR that is missing at least what's described in #39874 (review).

I would advise you to start by creating a new issue or a new GitHub discussion first explaining why this could be useful for the project.
By doing so, the idea can be discussed with the maintainers, and the development can start at the right time.

Even if your PR was perfect, we should wait until we're ready to start a new minor version (v5.4 for example) and couldn't (wouldn't have the time) to review it before.